From: Stephane Eranian <eranian@hpl.hp.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, ak@suse.de,
Stephane Eranian <eranian@hpl.hp.com>
Subject: Re: [PATCH] add i386 idle notifier (take 3)
Date: Tue, 9 Jan 2007 02:49:07 -0800 [thread overview]
Message-ID: <20070109104907.GE27034@frankl.hpl.hp.com> (raw)
In-Reply-To: <20070105133653.GS20714@stusta.de>
Hello,
On Fri, Jan 05, 2007 at 02:36:53PM +0100, Adrian Bunk wrote:
> > > > > 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?
> > >
> > None.
> >
> > I have no issue with removing the EXPORT_SYMBOL on i386 and x86_64 if you
> > think that would help.
>
As a follow-up to this discussion, here is a patch that remove unused
EXPORT_SYMBOL by the i386 idle notifier. It also make it more explicit
that the enter_idle() store must be atomic.
changelog:
- do not export i386 idle notification registration entry points
because there is currently no user for this
- make it more explicit that the store to idle_state must be atomic
signed-off-by: stephane eranian <eranian@hpl.hp.com>
--- linux-2.6.20-rc3-mm1.orig/arch/i386/kernel/process.c 2007-01-08 01:58:08.000000000 -0800
+++ linux-2.6.20-rc3-mm1/arch/i386/kernel/process.c 2007-01-08 02:01:59.000000000 -0800
@@ -87,19 +87,18 @@ void idle_notifier_register(struct notif
{
atomic_notifier_chain_register(&idle_notifier, n);
}
-EXPORT_SYMBOL_GPL(idle_notifier_register);
void idle_notifier_unregister(struct notifier_block *n)
{
atomic_notifier_chain_unregister(&idle_notifier, n);
}
-EXPORT_SYMBOL(idle_notifier_unregister);
static DEFINE_PER_CPU(volatile unsigned long, idle_state);
void enter_idle(void)
{
- __get_cpu_var(idle_state) = 1;
+ /* needs to be atomic w.r.t. interrupts, not against other CPUs */
+ __set_bit(0, &__get_cpu_var(idle_state));
atomic_notifier_call_chain(&idle_notifier, IDLE_START, NULL);
}
prev parent reply other threads:[~2007-01-09 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 14:05 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
2007-01-05 10:55 ` Stephane Eranian
2007-01-05 13:36 ` Adrian Bunk
2007-01-09 10:49 ` Stephane Eranian [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=20070109104907.GE27034@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--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
Powered by JetHome