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: Thu, 4 Jan 2007 00:07:08 +0100 [thread overview]
Message-ID: <20070103230708.GM20714@stusta.de> (raw)
In-Reply-To: <20070103132015.GE7238@frankl.hpl.hp.com>
On Wed, Jan 03, 2007 at 05:20:15AM -0800, Stephane Eranian wrote:
> Adrian,
>
> On Sat, Dec 23, 2006 at 12:40:15PM +0100, Adrian Bunk wrote:
> > >
> > > 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.
>
> I am hearing conflicting opinions on this one.
>
> Perfmon is a fairly big patch. It is hard to take it as one. I have tried to
> split it up in smaller, more manageable pieces as requested by top-level
> maintainers. This process implies that I supply small patches which may not
> necessarily have users just yet.
There should be a big patchset consisting of manageable pieces, if
possible all of it in -mm.
> > 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?
> > >
> > Where does the perfmon code use the EXPORT_SYMBOL's?
>
> The perfmon patch includes several kernel modules which make use of
> the exported entry points. The following symbols are exported:
>
> pfm_pmu_register/pfm_pmu_unregister:
> * PMU description module registration.
> * Used to describe PMU model.
> * Used by perfmon_p4.c, perfmon_core.c, perfmon_mckinley.c, and others
>
> pfm_fmt_register/pfm_fmt_unregister:
> * Sampling format module registration
> * Used by perfmon_dfl_smpl.c, perfmon_pebs_smpl.c
>
> pfm_interrupt_handler:
> * PMU interrupt handler
> * Used by MIPS-specific perfmon code
>
> pfm_pmu_conf/pfm_controls:
> * global state/control variable
>
> All exported symbols are currently used. Why are you saying this adds bloat?
Which module uses idle_notifier_register/idle_notifier_unregister?
> -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:[~2007-01-03 23:07 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
2007-01-03 13:20 ` Stephane Eranian
2007-01-03 23:07 ` Adrian Bunk [this message]
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=20070103230708.GM20714@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.