From: John Levon <levon@movementarian.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [4/7] oprofile - NMI hook
Date: Wed, 16 Oct 2002 17:36:54 +0100 [thread overview]
Message-ID: <20021016163654.GA85246@compsoc.man.ac.uk> (raw)
In-Reply-To: <32233.1034777200@ocs3.intra.ocs.com.au>
On Thu, Oct 17, 2002 at 12:06:40AM +1000, Keith Owens wrote:
> Both kdb and lkcd use cross cpu NMI for debugging and dumping on SMP.
> That plus oprofile and the NMI watchdog makes at least four users of
> NMI. A one level hook is not going to cut it, it should be a list.
>
> I admit that removal of a hook from the NMI list while still handling
> NMI interrupts is "interesting", but that is a SMOP ;). RCU to the
> rescue?
Yep, now RCU is merged I'll read up and see if I can come up with a list
API
regards
john
--
"It's a cardboard universe ... and if you lean too hard against it, you fall
through."
- Philip K. Dick
prev parent reply other threads:[~2002-10-16 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 22:33 [PATCH] [4/7] oprofile - NMI hook John Levon
2002-10-15 22:56 ` Andi Kleen
2002-10-15 23:01 ` John Levon
2002-10-15 23:18 ` Andi Kleen
2002-10-16 14:06 ` Keith Owens
2002-10-16 16:36 ` John Levon [this message]
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=20021016163654.GA85246@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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