mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NMI notifiers for 2.5
Date: 04 Dec 2002 21:08:59 +0100	[thread overview]
Message-ID: <p731y4xtulg.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Stephen Hemminger's message of "4 Dec 2002 19:46:37 +0100"

Stephen Hemminger <shemminger@osdl.org> writes:

> The following generalizes the NMI callback's needed by things like crash
> dump and debuggers in the same way that panic has notifiers. 
> 
> Please apply this since it makes writing and maintaining RAS extensions
> easier. Since there is already a panic_notifier callback, this follows
> the same model. 

> +			
> +			notifier_call_chain(&nmi_notifier_list, 0, regs);
> +

Most debuggers/crash dumpers etc. need a way to veto normal processing of NMIs 
and other exceptions. For NMI the usual case is to turn off the nmi watchdog 
while you do something slow with interrupts disabled, that requires
doing the hook very early. Without veta NMI notification is not very useful.

You want something like:

	if (notifier_call_chain(&nmi_notifier_list, 0, regs) == NOTIFY_BAD)
		goto ignore;

For a more comprehensive variant see include/asm-x86_64/kdebug.h	
The x86-64 variant cannot be 1:1 copied because it's still incomplete
and e.g. does not implement veto for all places where it's needed.


-Andi

       reply	other threads:[~2002-12-04 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1039027142.20387.11.camel@dell_ss3.pdx.osdl.net.suse.lists.linux.kernel>
2002-12-04 20:08 ` Andi Kleen [this message]
2002-12-04 21:54   ` Stephen Hemminger
2002-12-05  7:09     ` Andi Kleen
2002-12-04 19:20 Larry Sendlosky
2002-12-04 19:41 ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2002-12-04 18:39 Stephen Hemminger
2002-12-04 19:01 ` John Levon

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=p731y4xtulg.fsf@oldwotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@osdl.org \
    /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