All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
	Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] issues with debugging enabled
Date: Wed, 13 Nov 2013 09:23:44 +0100	[thread overview]
Message-ID: <52833710.5080407@xenomai.org> (raw)
In-Reply-To: <528290CE.1030002@xenomai.org>

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?

-- 
Philippe.


  reply	other threads:[~2013-11-13  8:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 20:34 [Xenomai] issues with debugging enabled Gilles Chanteperdrix
2013-11-13  8:23 ` Philippe Gerum [this message]
2013-11-13  8:37   ` Gilles Chanteperdrix
2013-11-13 11:55     ` Philippe Gerum
2013-11-13 13:25 ` Jan Kiszka
2013-11-13 13:41   ` Gilles Chanteperdrix
2013-11-13 13:53     ` Jan Kiszka
2013-11-14 19:36       ` Jan Kiszka
2013-11-14 20:23         ` Gilles Chanteperdrix
2013-11-18 13:01           ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52833710.5080407@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.