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 15:04:56 +0200	[thread overview]
Message-ID: <20090730150456.6c87b997@skybase> (raw)
In-Reply-To: <1248958173.6046.32.camel@desktop>

On Thu, 30 Jul 2009 05:49:33 -0700
Daniel Walker <dwalker@fifo99.com> wrote:

> On Thu, 2009-07-30 at 12:53 +0200, Martin Schwidefsky wrote:
> 
> > > I'm not sure allowing that type of override a good idea tho .. I don't
> > > think it's considered a usable clock when the rating goes to zero.
> > 
> > Override as the root user -> your foot, no? The whole override stuff is
> > there for the case that the clocksource selection picked a broken clock
> > and you want to force the system into a semi-working state. Ideally the
> > whole override would go away, but that is probably wishful thinking..
> 
> I would agree if the system doesn't crash as a result, if it just starts
> to operate funny then that's maybe acceptable. If you keep the change
> rating function, you could potentially remove the unregister path..

Why shouldn't it be possible to have a clocksource as a module? I think
that the unregister path should stay. To really make it work we'd need
a function to force the system out of the one-shot mode though.

-- 
blue skies,
   Martin.

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


  reply	other threads:[~2009-07-30 13:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200907291717.n6THHG6f001426@d06av06.portsmouth.uk.ibm.com>
2009-07-30 10:53 ` [RFC][patch 00/12] clocksource / timekeeping rework V2 Martin Schwidefsky
2009-07-30 12:49   ` Daniel Walker
2009-07-30 13:04     ` Martin Schwidefsky [this message]
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] <200907301349.n6UDnCpx008890@d06av06.portsmouth.uk.ibm.com>
2009-07-30 15:42 ` Martin Schwidefsky
     [not found] <200907291702.n6TH2LEt017305@d06av05.portsmouth.uk.ibm.com>
2009-07-29 17:09 ` Martin Schwidefsky
2009-07-29 17:17   ` Daniel Walker
2009-07-29 17:34   ` Daniel Walker
2009-07-30  7:42     ` Martin Schwidefsky
     [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=20090730150456.6c87b997@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.