public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vamsi Krishna S ." <vamsi@in.ibm.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Kernel List <linux-kernel@vger.kernel.org>,
	lkcd-devel@lists.sourceforge.net, ak@suse.de,
	cminyard@mvista.com, vamsi_krishna@in.ibm.com
Subject: Re: [PATCH] Notifier for significant events on i386
Date: Wed, 11 Dec 2002 16:51:53 +0530	[thread overview]
Message-ID: <20021211165153.A17546@in.ibm.com> (raw)
In-Reply-To: <1039471369.1055.161.camel@dell_ss3.pdx.osdl.net>; from shemminger@osdl.org on Mon, Dec 09, 2002 at 10:08:11PM +0000

On Mon, Dec 09, 2002 at 10:08:11PM +0000, Stephen Hemminger wrote:
> This is a successor to the previous patch for notifier callback when NMI
> watchdog occurs.  It is a port of x86_64 code (thanks for the suggestion
> Andi Kleen <ak@suse.de>) with extensions for watchdog, and integration
> of panic handling.  
> 
> To get notified for panic, oops, NMI and other events the caller needs
> to insert itself in the notify_die chain.  The callback can then filter
> out which events are of interest. 
> 
> This started out as a way to hook in LKCD, but it is general enough that
> kprobe, kdb, and other utilities can use it as well. 
> 
I support this, it makes all kernel-space debug tools less intrusive. 
It may be out of scope for this work but there are a couple of
other issues to consider here:

- turn trap1/trap3 to interrupt gates: kprobes does this, kgdb turns
  off interrupts in its own handler, I suppose other tools too need
  this.
- notifier lists are racy on SMP, IFAICT, read_lock(&notifier_lock)
  needs to be taken in notifier_call_chain(), but that too is 
  deadlock prone.

Andi,

Isn't this a problem on x86_64 too? What is there to prevent a
handler from being removed from the notifier list while it
is being used to call the handler on another CPU?

I am considering using a RCU-based list for notifier chains.
Corey has done some work on these lines to add NMI notifier
chain, I think it should be generalised on for all notifiers.

Thoughts? Comments?
-- 
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5044959
Internet: vamsi@in.ibm.com

  reply	other threads:[~2002-12-11 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 22:02 [PATCH] Notifier for significant events on i386 Stephen Hemminger
2002-12-11 11:21 ` Vamsi Krishna S . [this message]
2002-12-11 11:16   ` William Lee Irwin III
2002-12-11 11:43     ` Vamsi Krishna S .
2002-12-11 16:56       ` [lkcd-devel] " Stephen Hemminger
2002-12-11 20:27       ` John Levon
2002-12-11 21:15         ` Alan Cox
2002-12-12  0:19           ` Stephen Hemminger
2002-12-12  7:34             ` Vamsi Krishna S .
2002-12-12 17:53               ` Stephen Hemminger
2002-12-12 17:58                 ` John Levon
2002-12-13 12:32                   ` Vamsi Krishna S .
2002-12-12  8:13           ` Vamsi Krishna S .
2002-12-11 13:57   ` Corey Minyard

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=20021211165153.A17546@in.ibm.com \
    --to=vamsi@in.ibm.com \
    --cc=ak@suse.de \
    --cc=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkcd-devel@lists.sourceforge.net \
    --cc=shemminger@osdl.org \
    --cc=vamsi_krishna@in.ibm.com \
    /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