public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	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: Fri, 29 May 2009 01:58:16 +0900	[thread overview]
Message-ID: <20090528165816.GA31688@linux-sh.org> (raw)
In-Reply-To: <1243529547.28705.43.camel@desktop>

On Thu, May 28, 2009 at 09:52:27AM -0700, Daniel Walker wrote:
> On Fri, 2009-05-29 at 01:40 +0900, Paul Mundt wrote:
> > On Thu, May 28, 2009 at 06:32:09PM +0200, Peter Zijlstra wrote:
> > > On Thu, 2009-05-28 at 09:13 -0700, Daniel Walker wrote:
> > > > On Thu, 2009-05-28 at 14:59 +0200, Peter Zijlstra wrote:
> > > > > CPU0                           CPU1
> > > > > 
> > > > > clock = ACCESS_ONCE(sched_clocksource);
> > > > > 
> > > > >                                unload module
> > > > >                                  clocksource_unregister()
> > > > >                                    sched_clocksource = jiffies
> > > > >                                  unmap data/text
> > > > > 
> > > > > cyc2ns(clock, clocksource_read(clock)) <--- fireworks
> > > > > 
> > > > > 
> > > > 
> > > > Do any module based clocksources even exist right now?
> > > > clocksource_unregister only seems to be used 3 times..
> > > 
> > > Good point, it appears its not even exported.
> > > 
> > > Thomas mentioned modules, I assumed.
> > > 
> > The drivers/clocksource/ drivers in theory could be modular anyways.
> > Handling this transition properly is at least one less barrier to modular
> > clocksources, so I think it's progress regardless. I don't remember what
> > all of the other issues were though, John probably remembers.
> 
> I don't think it's an important case to consider right now ..
> clocksources are usually so integral to the system putting one in a
> module seems counterintuitive. 
> 
I would not have mentioned it if it weren't something we already had use
cases for. For the SH timers alone we have 3 that can be used as
clocksources in any combination, excluding the differences in timer
channels per block. These tend to have different implications for
performance, power management, etc.

The only reason they are not modular today is because more work needs to
be done to handle clocksources going away, or at least there was the last
time we tried it.

  reply	other threads:[~2009-05-28 16:58 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
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 [this message]
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=20090528165816.GA31688@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@linux-foundation.org \
    --cc=dwalker@fifo99.com \
    --cc=hskinnemoen@atmel.com \
    --cc=johnstul@linux.vnet.ibm.com \
    --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=peterz@infradead.org \
    --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