From: Adrian Bunk <bunk@stusta.de>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [PATCH] add i386 idle notifier (take 3)
Date: Sat, 23 Dec 2006 12:40:15 +0100 [thread overview]
Message-ID: <20061223114015.GQ6993@stusta.de> (raw)
In-Reply-To: <20061222100700.GB1895@frankl.hpl.hp.com>
On Fri, Dec 22, 2006 at 02:07:00AM -0800, Stephane Eranian wrote:
> Andrian,
>
> On Fri, Dec 22, 2006 at 02:06:41AM +0100, Adrian Bunk wrote:
> > > changelog:
> > > - add a notifier mechanism to the low level idle loop. You can
> > > register a callback function which gets invoked on entry and exit
> > > from the low level idle loop. The low level idle loop is defined as
> > > the polling loop, low-power call, or the mwait instruction. Interrupts
> > > processed by the idle thread are not considered part of the low level
> > > loop. The notifier can be used to measure precisely how much is spent
> > > in useless execution (or low power mode). The perfmon subsystem uses it
> > > to turn on/off monitoring.
> >
> >
> > Why is this patch not submitted as part of the perfmon patch that also
> > adds a user of this code?
>
> If you look at the perfmon-new-base patch, you'll see a base.diff patch which
> includes this one. I am slowly getting rid of this requirement by pushing
> those "infrastructure patches" to mainline so that the perfmon patch gets
> smaller over time. Submitting smaller patches makes it easier for maintainers
> to integrate.
No, the preferred way is to start with getting both the infrastructure
and the users into -mm.
Adding infrastructure without users doesn't fit into the kernel
development model.
The unused x86-64 idle notifiers are now bloating the kernel since
nearly one year.
> > And why does it bloat the kernel with EXPORT_SYMBOL's although even your
> > perfmon-new-base-061204 doesn't seem to add any modular user?
>
> I have tried to stay as close as possible from the x86-64 implementation
> of this mechanism. The registration entry points are exported to modules,
> just like they are for x86-64. Also note that the x86-64 idle notifier does
> not have a user at this point, yet it is in the kernel. Perfmon will become
> the first user of this mechanism.
Where does the perfmon code use the EXPORT_SYMBOL's?
And having added bloat on one architecture is not an excuse for adding
bloat on other architectures.
> -Stephane
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-12-23 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 14:05 [PATCH] add i386 idle notifier (take 3) Stephane Eranian
2006-12-21 5:05 ` Andrew Morton
2006-12-21 9:12 ` Stephane Eranian
2006-12-22 1:06 ` Adrian Bunk
2006-12-22 10:07 ` Stephane Eranian
2006-12-23 11:40 ` Adrian Bunk [this message]
2007-01-03 13:20 ` Stephane Eranian
2007-01-03 23:07 ` Adrian Bunk
2007-01-05 10:55 ` Stephane Eranian
2007-01-05 13:36 ` Adrian Bunk
2007-01-09 10:49 ` 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=20061223114015.GQ6993@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=eranian@hpl.hp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.