From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <52833A47.2000009@xenomai.org> Date: Wed, 13 Nov 2013 09:37:27 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <528290CE.1030002@xenomai.org> <52833710.5080407@xenomai.org> In-Reply-To: <52833710.5080407@xenomai.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] issues with debugging enabled List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Gerum Cc: Xenomai On 11/13/2013 09:23 AM, Philippe Gerum wrote: > On 11/12/2013 09:34 PM, Gilles Chanteperdrix wrote: >> >> Hi, >> >> for a change, I ran the xeno-regression-test with a lot of debugging and >> options known to having caused problems in the past and found two issues: >> >> on x86 SMP, with full dynticks and debugging enabled (preemptible kernel >> debugging, mutex, spinlocks, and sleep inside spinlocks), I get the >> series of warnings at the end of the mail. > > Our IRQ deferral might conflict with the RCU state logic (e.g. > rcu-irq_enter/exit). > >> >> on ARM, when a fault occurs, the fault ode is entered with hardware irqs >> off (this is a recent change in the mainline kernel, this code used to >> be executed with hardware irqs on), so I do: >> >> ipipe_stall_root(); >> hard_local_irq_enabled(); >> >> But the context checking does not like that. >> > > You mean ipipe_root_only() triggers over the stall point? > Yes, because ipipe_stall_root() is called with hw irqs off if I understand correctly. -- Gilles.