From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Paul Mundt <lethal@linux-sh.org>,
Daniel Walker <dwalker@fifo99.com>,
Linus Walleij <linus.ml.walleij@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Andrew Victor <linux@maxim.org.za>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk,
John Stultz <johnstul@linux.vnet.ibm.com>
Subject: Re: [PATCH] sched: Support current clocksource handling in fallback sched_clock().
Date: Thu, 28 May 2009 14:40:16 +0200 [thread overview]
Message-ID: <1243514416.6600.74.camel@laptop> (raw)
In-Reply-To: <alpine.LFD.2.00.0905281417500.3397@localhost.localdomain>
On Thu, 2009-05-28 at 14:22 +0200, Thomas Gleixner wrote:
> On Thu, 28 May 2009, Paul Mundt wrote:
> > @@ -437,10 +441,19 @@ void clocksource_unregister(struct clocksource *cs)
> > unsigned long flags;
> >
> > spin_lock_irqsave(&clocksource_lock, flags);
> > +
> > + if (sched_clocksource == cs) {
> > + printk(KERN_WARNING "Refusing to unregister "
> > + "scheduler clocksource %s", cs->name);
>
> Hmm, isn't that dangerous ? The clocksource might be in a module or
> in kmalloced memory which is going to be freed.
One could play dirty tricks with 'leaking' module ref counts and such so
as to avoid that. The alternative is making sched_clock() look something
like:
u64 __weak sched_clock(void)
{
struct clocksource *clock;
u64 time;
rcu_read_lock();
clock = rcu_dereference(sched_clocksource);
time = cyc2ns(clock, read_clocksource(clock));
rcu_read_unlock;
return time;
}
and make the module unload do a sync_rcu -- but this might be a little
overkill
next prev parent reply other threads:[~2009-05-28 12:40 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 6:15 [PATCH] sched: Support current clocksource handling in fallback sched_clock() Paul Mundt
2009-05-26 14:31 ` Linus Walleij
2009-05-26 14:38 ` Peter Zijlstra
2009-05-26 20:17 ` Thomas Gleixner
2009-05-26 23:08 ` Paul Mundt
2009-05-26 23:13 ` Paul Mundt
2009-05-26 23:25 ` john stultz
2009-05-26 23:44 ` Paul Mundt
2009-05-27 0:18 ` Thomas Gleixner
2009-05-27 0:22 ` john stultz
2009-05-27 0:26 ` Paul Mundt
2009-05-27 1:09 ` john stultz
2009-05-27 0:27 ` Thomas Gleixner
2009-05-26 23:49 ` Thomas Gleixner
2009-05-27 0:15 ` Paul Mundt
2009-05-27 16:25 ` Daniel Walker
2009-05-28 8:44 ` Paul Mundt
2009-05-28 9:19 ` Paul Mundt
2009-05-28 9:34 ` Peter Zijlstra
2009-05-28 11:09 ` Paul Mundt
2009-05-28 12:22 ` Thomas Gleixner
2009-05-28 12:40 ` Peter Zijlstra [this message]
2009-05-28 12:42 ` Paul Mundt
2009-05-28 12:53 ` Thomas Gleixner
2009-05-28 12:59 ` Peter Zijlstra
2009-05-28 13:20 ` Paul Mundt
2009-05-28 16:13 ` Daniel Walker
2009-05-28 16:32 ` Peter Zijlstra
2009-05-28 16:40 ` Paul Mundt
2009-05-28 16:52 ` Daniel Walker
2009-05-28 16:58 ` Paul Mundt
2009-05-28 17:38 ` Daniel Walker
2009-05-28 17:46 ` Thomas Gleixner
2009-05-28 17:53 ` Paul Mundt
2009-05-28 18:10 ` Daniel Walker
2009-05-28 18:27 ` Paul Mundt
2009-05-28 19:04 ` Daniel Walker
2009-05-28 19:34 ` Paul Mundt
2009-05-28 19:41 ` Daniel Walker
2009-05-28 23:37 ` Paul Mundt
2009-05-28 18:44 ` Thomas Gleixner
2009-05-28 17:00 ` Thomas Gleixner
2009-05-28 17:07 ` John Stultz
2009-05-26 20:23 ` john stultz
2009-05-26 20:30 ` Peter Zijlstra
2009-05-26 20:40 ` john stultz
2009-05-26 20:55 ` Peter Zijlstra
2009-05-26 23:00 ` john stultz
2009-05-26 23:24 ` Mangalampalli, JayantX
2009-05-27 0:04 ` Thomas Gleixner
2009-05-26 23:39 ` Thomas Gleixner
2009-05-27 6:58 ` Peter Zijlstra
2009-05-26 20:39 ` Thomas Gleixner
2009-05-26 14:43 ` Paul Mundt
2009-05-26 14:50 ` Peter Zijlstra
2009-05-26 14:53 ` Paul Mundt
2009-05-26 15:02 ` Matthieu CASTET
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=1243514416.6600.74.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dwalker@fifo99.com \
--cc=hskinnemoen@atmel.com \
--cc=johnstul@linux.vnet.ibm.com \
--cc=lethal@linux-sh.org \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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