From: Christoph Lameter <clameter@engr.sgi.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Rusty Lynch <rusty@linux.intel.com>, Andi Kleen <ak@suse.de>,
Rusty Lynch <rusty.lynch@intel.com>,
linux-mm@kvack.org, prasanna@in.ibm.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured.
Date: Mon, 19 Sep 2005 11:22:04 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0509191119020.25963@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20050830111830.GI26314@parcelfarce.linux.theplanet.co.uk>
On Tue, 30 Aug 2005, Matthew Wilcox wrote:
> On Mon, Aug 29, 2005 at 05:19:05PM -0700, Rusty Lynch wrote:
> > So, assuming inlining the notifier_call_chain would address Christoph's
> > conserns, is the following patch something like what you are sugesting?
> > This would make all the kdebug.h::notify_die() calls use the inline version.
>
> I think we need something more like this ...
>
> include/linux/notifier.h:
> +static inline int notifier_call_chain(struct notifier_block **n,
> + unsigned long val, void *v)
> +{
> + if (n)
> + return __notifier_call_chain(n, val, v);
> + return NOTIFY_DONE;
> +}
> kernel/sys.c:
> -int notifier_call_chain(struct notifier_block **n, unsigned long val, void *v)
> +int __notifier_call_chain(struct notifier_block **n, unsigned long val, void *v)
> -EXPORT_SYMBOL(notifier_call_chain);
> +EXPORT_SYMBOL(__notifier_call_chain);
>
> That way everyone gets both the quick test and the global size reduction.
And then do
#ifndef CONFIG_KPROBES
#define ia64die_chain 0
#endif
in include/asm-ia64/kdebug.h?
Otherwise we still check a notifier chain that cannot ever be
activated.
But then the patch is essentially the same as the last one I proposed.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-09-19 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 22:46 Rusty Lynch
2005-08-26 23:05 ` Christoph Lameter
2005-08-27 0:24 ` [PATCH] " Andi Kleen
2005-08-30 0:19 ` Rusty Lynch
2005-08-30 1:08 ` Andi Kleen
2005-08-30 3:28 ` Christoph Lameter
2005-08-30 11:18 ` Matthew Wilcox
2005-09-19 18:22 ` Christoph Lameter [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-30 23:05 Luck, Tony
2005-08-30 23:38 ` Andi Kleen
2005-08-30 23:54 ` Christoph Lameter
2005-08-31 0:05 ` Andi Kleen
2005-08-25 20:14 Christoph Lameter
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=Pine.LNX.4.62.0509191119020.25963@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=ak@suse.de \
--cc=anil.s.keshavamurthy@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
--cc=prasanna@in.ibm.com \
--cc=rusty.lynch@intel.com \
--cc=rusty@linux.intel.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