From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stephane Eranian <eranian@hpl.hp.com>,
linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [PATCH] i386 add idle notifier
Date: Wed, 29 Nov 2006 13:09:44 -0800 [thread overview]
Message-ID: <20061129130944.82e3d9bb.akpm@osdl.org> (raw)
In-Reply-To: <20061129170939.GA29203@infradead.org>
On Wed, 29 Nov 2006 17:09:39 +0000
Christoph Hellwig <hch@infradead.org> wrote:
> On Wed, Nov 29, 2006 at 08:25:40AM -0800, Stephane Eranian wrote:
> > Hello,
> >
> > Here is a patch that adds an idle notifier to the i386 tree.
> > The idle notifier functionalities and implementation are
> > identical to the x86_64 idle notifier. We use the idle notifier
> > in the context of perfmon.
> >
> > The patch is against Andi Kleen's x86_64-2.6.19-rc6-061128-1.bz2
> > kernel. It may apply to other kernels but it needs some updates
> > to poll_idle() and default_idle() to work correctly.
>
> Walking through a notifier chain on every single interrupt (including
> timer interrupts) seems rather costly. What do you need this for
> exactly?
yes, it's a worry.
Why doesn't enter_idle() do the test_and_set_bit() thing, like
exit_idle()?
next prev parent reply other threads:[~2006-11-29 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 16:25 [PATCH] i386 add idle notifier Stephane Eranian
2006-11-29 16:37 ` Andi Kleen
2006-11-29 16:41 ` [PATCH] i386 add idle notifier (take 2) Stephane Eranian
2006-11-29 17:09 ` [PATCH] i386 add idle notifier Christoph Hellwig
2006-11-29 21:09 ` Andrew Morton [this message]
2006-11-29 22:18 ` Stephane Eranian
2006-11-29 23:05 ` Andrew Morton
2006-11-29 23:15 ` Russell King
2006-11-29 23:21 ` Andi Kleen
2006-11-30 8:16 ` Stephane Eranian
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=20061129130944.82e3d9bb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=eranian@hpl.hp.com \
--cc=hch@infradead.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