On Fri, 2006-11-17 at 20:10 +0100, Jan Kiszka wrote:
> Philippe Gerum wrote:
> > On Fri, 2006-11-17 at 19:41 +0100, Jan Kiszka wrote:
> >> I'm currently seeing two potential "misuses" of the common switch:
> >>
> >>  - the posix skin (Gilles, how heavy-weighted are those checks?)
> >>    => CONFIG_XENO_OPT_DEBUG_POSIX
> >>
> >>  - CONFIG_XENO_SPINLOCK_DEBUG => CONFIG_XENO_OPT_DEBUG_SPINLOCK
> >>
> >> Both should be explicitly controllable in Kconfig.
> >>
> > 
> > Nack for CONFIG_XENO_OPT_DEBUG_SPINLOCK. Most of the issue we tracked
> > with Gilles regarding the domain migration code had side-effects on the
> > nucleus lock. So having CONFIG_XENO_OPT_DEBUG enabled for identifying
> > internal state weirdnesses - like those triggered by migration bugs -
> > implies enabling the spinlock watchdogs too.
> 
> Ok, if it only makes sense to have both enabled at the same time, then
> let us create XENO_OPT_DEBUG_NUCLEUS. It should include both, but it
> shall not be automatically on when, say, only XENO_OPT_DEBUG_RTDM is
> required.

No objection.

> 
> Jan
> 
-- 
Philippe.



_______________________________________________
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core

Reply via email to