From: Peter Zijlstra <peterz@infradead.org>
To: Julien Thierry <julien.thierry@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
ricardo.neri-calderon@linux.intel.com, marc.zyngier@arm.com,
mingo@kernel.org
Subject: Re: [RFC PATCH 1/4] genirq: Provide basic NMI management for interrupt lines
Date: Tue, 17 Jul 2018 13:28:42 +0200 [thread overview]
Message-ID: <20180717112842.GT2476@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <e0c00482-7125-32e5-faa1-4251c118de5e@arm.com>
On Tue, Jul 17, 2018 at 12:13:44PM +0100, Julien Thierry wrote:
> I'm a bit unsure about this one. In practice NMI handlers shouldn't take
> forever nor block the system for too long.
On x86 at least, kgdb can be in NMI context for extended periods. Not
saying that's a good thing, but on occasion we get reports on stuff
coming apart because of that.
(most times we tell people to not do that then)
next prev parent reply other threads:[~2018-07-17 11:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 16:14 [RFC PATCH 0/4] Provide core API for NMIs Julien Thierry
2018-07-09 16:14 ` [RFC PATCH 1/4] genirq: Provide basic NMI management for interrupt lines Julien Thierry
2018-07-17 9:22 ` Thomas Gleixner
2018-07-17 11:13 ` Julien Thierry
2018-07-17 11:28 ` Peter Zijlstra [this message]
2018-07-17 12:25 ` Julien Thierry
2018-07-17 15:48 ` Julien Thierry
2018-07-17 15:51 ` Peter Zijlstra
2018-07-17 16:35 ` Julien Thierry
2018-07-17 19:46 ` Thomas Gleixner
2018-07-18 8:09 ` Julien Thierry
2018-07-17 19:42 ` Thomas Gleixner
2018-07-09 16:14 ` [RFC PATCH 2/4] genirq: Provide NMI management for percpu_devid interrupts Julien Thierry
2018-07-09 16:14 ` [RFC PATCH 3/4] genirq: Provide NMI handlers Julien Thierry
2018-07-09 16:14 ` [RFC PATCH 4/4] irqdesc: Add domain handler for NMIs Julien Thierry
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=20180717112842.GT2476@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=julien.thierry@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome