From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, minyard@acm.org, dvhltc@us.ibm.com,
niv@us.ibm.com
Subject: Re: Recoverable MCA interrupts from NMI handlers? IPMI and RCU?
Date: Fri, 6 Jun 2008 09:41:22 -0700 [thread overview]
Message-ID: <20080606164122.GD8507@linux.vnet.ibm.com> (raw)
In-Reply-To: <484961FC.5030800@zytor.com>
On Fri, Jun 06, 2008 at 09:12:44AM -0700, H. Peter Anvin wrote:
> 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).
>
> In theory, recoverable #MC's can occur anywhere. It's an exception.
Thank you for the info! I guess I had better get busy testing the
patch, then.
> >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.
>
> Not sure about that one. I clearly need to look carefully into this...
> SMI is quite "special" in that it sets up an entirely new environment;
> the concept of executing kernel code at SMI level makes me want to run
> away and hide.
Well, as long as the SMI handlers don't include calls to rcu_read_lock()
and rcu_read_unlock(), then they don't need to include any calls to
rcu_irq_enter() and rcu_irq_exit(). ;-)
Thanx, Paul
next prev parent reply other threads:[~2008-06-06 16:41 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 [this message]
2008-06-06 17:04 ` Maciej W. Rozycki
2008-06-06 20:53 ` Corey Minyard
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=20080606164122.GD8507@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=minyard@acm.org \
--cc=niv@us.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 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.