From: Christoph Hellwig <hch@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: PATCH] debug: add notifier chain debugging
Date: Fri, 22 Aug 2008 10:45:16 -0400 [thread overview]
Message-ID: <20080822144516.GA12479@infradead.org> (raw)
In-Reply-To: <20080822070054.5d466be9@infradead.org>
On Fri, Aug 22, 2008 at 07:00:54AM -0700, Arjan van de Ven wrote:
> On Tue, 19 Aug 2008 21:09:32 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> >
> > If we remove the first two checks then surely we can afford to add the
> > remaining check unconditionally and lose the new config option and its
> > ifdef.
> >
>
> Andi told me that this notifier is a hotpath for kprobes (systemtap)
> use models; at which point making this a config option makes sort of
> sense to get the last bit of performance out of that. Personally I would
> always want this option on for anything I run, and I suspect
> (enterprise) distros will just always turn it on as well since it's a
> good sanity check at low cost.
>
> I'd be happy to lose the config (I think we have way too many unneeded
> ones of those already); I'll make a patch.
What about checking yourself? At least the braindead use of notiiers in
the pagefault path for kprobes (even unconditional on x86_64) is gone
now and replaced with proper kprobes hooks. The die notifier that's
also used by kprobes shouldn't be in a performance critical path.
next prev parent reply other threads:[~2008-08-22 14:45 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 [this message]
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
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=20080822144516.GA12479@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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