From: Paul Mackerras <paulus@samba.org>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move die notifier handling to common code
Date: Mon, 26 Mar 2007 11:32:09 +1000 [thread overview]
Message-ID: <17927.8857.752570.69739@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20070319160218.GA27462@lst.de>
Christoph Hellwig writes:
> This patch moves the die notifier handling to common code. Previous
> various architectures had exactly the same code for it. Note that
> the new code is compiled unconditionally, this should be understood
> as an appel to the other architecture maintainer to implement
> support for it aswell (aka sprinkling a notify_die or two in the
> proper place)
Seems OK, although I think kprobes should not be using notify_die.
The set of events that kprobes is interested in has no intersection at
all with the set that any other consumer of the notify_die events is
interested in, on any architecture.
Furthermore, the multiplexing of the kprobes events through notify_die
really serves no useful purpose. It just means that
kprobe_exceptions_notify has to demultiplex the events with a switch
statement. There is no significant common code for all events in
kprobe_exceptions_notify, just a simple check whether the event
happened in user mode.
However, all that is in arch code so can be changed per-arch if
desired.
Paul.
next prev parent reply other threads:[~2007-03-26 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 16:02 Christoph Hellwig
2007-03-26 1:32 ` Paul Mackerras [this message]
2007-03-26 6:55 ` Christoph Hellwig
2007-04-09 10:30 ` Paul Mackerras
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=17927.8857.752570.69739@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--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
all inboxes | Powered by JetHome®