From: Keith Owens <kaos@ocs.com.au>
To: John Levon <levon@movementarian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [4/7] oprofile - NMI hook
Date: Thu, 17 Oct 2002 00:06:40 +1000 [thread overview]
Message-ID: <32233.1034777200@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 15 Oct 2002 23:33:19 +0100." <20021015223319.GD41906@compsoc.man.ac.uk>
On Tue, 15 Oct 2002 23:33:19 +0100,
John Levon <levon@movementarian.org> wrote:
>This patch provides a simple api to let oprofile hook into
>the NMI interrupt for the perfctr profiler.
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?
next prev parent reply other threads:[~2002-10-16 14:00 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 [this message]
2002-10-16 16:36 ` 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=32233.1034777200@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=levon@movementarian.org \
--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