From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Tony Luck <tony.luck@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: PATCH] debug: add notifier chain debugging
Date: Wed, 27 Aug 2008 03:55:01 -0700 [thread overview]
Message-ID: <20080827035501.4b8cc732@infradead.org> (raw)
In-Reply-To: <20080827063915.GC6255@elte.hu>
On Wed, 27 Aug 2008 08:39:15 +0200
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Arjan van de Ven <arjan@infradead.org> wrote:
>
> > The patch below fixes this;
> > Ingo, please replace the patch with this one.
>
> well, this one is now less than cheap on x86:
really it isn't; dereference_function_descriptor is a fall through and
basically free.
>
> as it's rather large. So i kept the config option, and it defaults to
> off.
huh? the consensus was that the config needed to go ... nothing changed
on that front. I agree absolutely with not introducing config options
for things that don't need it; we have too many already anyway.
>
> > + if (!func_ptr_is_kernel_text(nb->notifier_call)) {
> > + WARN(1, "Invalid notifier called!");
> > + nb = next_nb;
> > + continue;
> > + }
>
> and that should be an unlikely() too i guess.
please do not add new unlikely()'s to the kernel.. not on non-hotpaths
at least
prev parent reply other threads:[~2008-08-27 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 22:29 PATCH] debug: add notifier chain debugging Arjan van de Ven
2008-08-15 22:53 ` Ingo Molnar
2008-08-20 4:09 ` Andrew Morton
2008-08-20 10:53 ` Ingo Molnar
2008-08-22 14:00 ` Arjan van de Ven
2008-08-22 14:45 ` Christoph Hellwig
2008-08-25 22:39 ` Tony Luck
2008-08-26 4:55 ` Arjan van de Ven
2008-08-26 5:08 ` Tony Luck
2008-08-26 13:46 ` Arjan van de Ven
2008-08-26 16:22 ` Arjan van de Ven
2008-08-27 6:39 ` Ingo Molnar
2008-08-27 10:55 ` Arjan van de Ven [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=20080827035501.4b8cc732@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@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