From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: paulmck@linux.vnet.ibm.com, John Stultz <john.stultz@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: RCU lockup in the SMP idle thread, help...
Date: Thu, 20 Sep 2012 13:49:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.02.1209201056531.6667@xanadu.home> (raw)
In-Reply-To: <CACRpkdaOG59CNvqUGFer+1TcVM8ovJwxmc3ZryJKw--PJ=bzsQ@mail.gmail.com>
On Thu, 20 Sep 2012, Linus Walleij wrote:
> On Thu, Sep 20, 2012 at 2:03 AM, Paul E. McKenney
> <paulmck@linux.vnet.ibm.com> wrote:
>
> > Any thoughts on the feasibility of implementing NMI-based stack backtraces
> > for ARM?
>
> Nico's department, so let's page him.
That _could_ be done, at least in theory, with some restrictions.
However in practice ...
> In IIRC ux500 all NMIs are reserved for the secure world, so it's
> basically a no can do. :-(
That's the main issue here: not all platforms allow FIQs ( a FIQ is the
closest to a NMI on ARM) to be available to the operating system.
However, for where this is possible, there is a patch series from Anton
Vorontsov implementing FIQ based KGDB support which might be useful
here.
Nicolas
next prev parent reply other threads:[~2012-09-20 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 12:36 Linus Walleij
2012-09-13 16:49 ` John Stultz
2012-09-13 16:58 ` Paul E. McKenney
2012-09-14 7:27 ` Linus Walleij
2012-09-14 17:53 ` Paul E. McKenney
2012-09-17 9:10 ` Linus Walleij
2012-09-20 0:03 ` Paul E. McKenney
2012-09-20 8:46 ` Linus Walleij
2012-09-20 17:49 ` Nicolas Pitre [this message]
2012-09-20 9:07 ` Linus Walleij
2012-09-20 14:10 ` Paul E. McKenney
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=alpine.LFD.2.02.1209201056531.6667@xanadu.home \
--to=nicolas.pitre@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®