From: Corey Minyard <minyard@acm.org>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, dvhltc@us.ibm.com,
niv@us.ibm.com
Subject: Re: Recoverable MCA interrupts from NMI handlers? IPMI and RCU?
Date: Fri, 06 Jun 2008 15:53:00 -0500 [thread overview]
Message-ID: <4849A3AC.5090107@acm.org> (raw)
In-Reply-To: <20080606152134.GA13641@linux.vnet.ibm.com>
Paul E. McKenney wrote:
> Hello!
>
> A couple of questions about the x86 architecture...
>
> 1. Can recoverable machine-check exceptions occur from within
> NMI handlers? If so, there is a bug in preemptable RCU's
> CONFIG_NO_HZ handling that could be fixed by a patch something
> like the one shown below (untested, probably does not even
> compile).
>
> 2. Does the IPMI subsystem make use of RCU read-side primitives
> from within SMI handlers? If so, we need the SMI handlers to
> invoke rcu_irq_enter() upon entry and rcu_irq_exit() upon exit
> when they are invoked from dynticks idle state. Or something
> similar, depending on restrictions on code within SMI handlers.
>
If you mean the IPMI driver, it does not tie into any SMI. It
theoretically could since there's a bit for that in the watchdog timer,
but there's been no demand and I haven't looked at it. I guess it would
be better than an NMI.
If it did tie in, it would most likely just panic to get useful
information out before the watchdog reset the system.
-corey
next prev parent reply other threads:[~2008-06-06 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 15:21 Recoverable MCA interrupts from NMI handlers? IPMI and RCU? Paul E. McKenney
2008-06-06 16:12 ` H. Peter Anvin
2008-06-06 16:41 ` Paul E. McKenney
2008-06-06 17:04 ` Maciej W. Rozycki
2008-06-06 20:53 ` Corey Minyard [this message]
2008-06-06 21:33 ` Paul E. McKenney
2008-06-07 0:03 ` H. Peter Anvin
2008-06-07 0:44 ` 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=4849A3AC.5090107@acm.org \
--to=minyard@acm.org \
--cc=dvhltc@us.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.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