public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Corey Minyard <minyard@acm.org>
Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, mingo@redhat.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 17:03:37 -0700	[thread overview]
Message-ID: <4849D059.1000701@zytor.com> (raw)
In-Reply-To: <4849A3AC.5090107@acm.org>

Corey Minyard wrote:
> 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.

The main reason I could see wanting to use SMI would be as a debugging 
tool, since SMI makes the entire state of the system available at a low 
level; however, trying to interact with the state of the kernel at this 
priority level seems beyond the pale in terms of complexity.

	-hpa

  parent reply	other threads:[~2008-06-07  0:10 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
2008-06-06 21:33   ` Paul E. McKenney
2008-06-07  0:03   ` H. Peter Anvin [this message]
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=4849D059.1000701@zytor.com \
    --to=hpa@zytor.com \
    --cc=dvhltc@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=minyard@acm.org \
    --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