All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Daniel Walker <dwalker@fifo99.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	john stultz <johnstul@us.ibm.com>
Subject: Re: [RFC][patch 00/12] clocksource / timekeeping rework V2
Date: Thu, 30 Jul 2009 09:42:50 +0200	[thread overview]
Message-ID: <20090730094250.3885961d@skybase> (raw)
In-Reply-To: <1248888877.6046.11.camel@desktop>

On Wed, 29 Jul 2009 10:34:37 -0700
Daniel Walker <dwalker@fifo99.com> wrote:

> On Wed, 2009-07-29 at 19:09 +0200, Martin Schwidefsky wrote:
> > On Wed, 29 Jul 2009 11:02:21 -0600
> > dwalker@fifo99.com wrote:
> > 
> > > On Wed, 2009-07-29 at 18:50 +0200, Martin Schwidefsky wrote:
> > > 
> > > > void clocksource_change_rating(struct clocksource *cs, int rating)
> > > 
> > > > the two functions do different things. What exactly is the idea you've
> > > > got in mind?
> > > 
> > > It's only the case when the rating goes to zero .. That makes the
> > > clocksource unusable, which is very much like unregistering it..
> > 
> > True, the clocksource code won't pick the clock any more as long as
> > there is an alternative clock available. It still shows up in the list
> > of clocks though and you can do an override with it. 
> 
> Now that you mention it, if the clocks are sorted by rating (something
> your removing) then the sysfs override available listing isn't in rated
> order .. So if you do have zero rated clocks you wouldn't have any idea
> from looking at the available list.. It could be solved just by printing
> them in rated order in the sysfs code tho.

Ok, I'll readd the sorting. It is a user visible change after all.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.


  reply	other threads:[~2009-07-30  7:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200907291702.n6TH2LEt017305@d06av05.portsmouth.uk.ibm.com>
2009-07-29 17:09 ` [RFC][patch 00/12] clocksource / timekeeping rework V2 Martin Schwidefsky
2009-07-29 17:17   ` Daniel Walker
2009-07-29 17:34   ` Daniel Walker
2009-07-30  7:42     ` Martin Schwidefsky [this message]
     [not found] <200907301349.n6UDnCpx008890@d06av06.portsmouth.uk.ibm.com>
2009-07-30 15:42 ` Martin Schwidefsky
     [not found] <200907291717.n6THHG6f001426@d06av06.portsmouth.uk.ibm.com>
2009-07-30 10:53 ` Martin Schwidefsky
2009-07-30 12:49   ` Daniel Walker
2009-07-30 13:04     ` Martin Schwidefsky
2009-07-30 13:49       ` Daniel Walker
2009-07-30 17:16         ` john stultz
2009-07-30 18:08           ` Daniel Walker
2009-07-30 20:37             ` Andreas Mohr
2009-07-30 20:56             ` john stultz
2009-07-31  5:33               ` Daniel Walker
2009-07-31  8:34                 ` john stultz
2009-07-31 16:44                   ` Daniel Walker
2009-07-30 17:12   ` john stultz
     [not found] <200907291510.n6TFAV8k000647@d06av06.portsmouth.uk.ibm.com>
2009-07-29 16:50 ` Martin Schwidefsky
2009-07-29 17:02   ` Daniel Walker
2009-07-29 13:41 Martin Schwidefsky
2009-07-29 15:10 ` Daniel Walker

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=20090730094250.3885961d@skybase \
    --to=schwidefsky@de.ibm.com \
    --cc=dwalker@fifo99.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.