public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Glauber de Oliveira Costa <gcosta@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	--cc@redhat.com, Ingo Molnar <mingo@elte.hu>,
	avi@quramnet.com, kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH] raise tsc clocksource rating
Date: Mon, 29 Oct 2007 18:26:56 -0700	[thread overview]
Message-ID: <1193707616.11323.6.camel@localhost> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710292315280.3186@localhost.localdomain>

On Mon, 2007-10-29 at 23:17 +0100, Thomas Gleixner wrote:
> On Mon, 29 Oct 2007, Glauber de Oliveira Costa wrote:
> 
> CC'ed John and removed glauber@t60.localdomain :)
> 
> > From: Glauber de Oliveira Costa <glauber@t60.localdomain>
> > 
> > tsc is very good time source (when it does not have drifts, does not
> > change it's frequency, i.e. when it works), so it should have its rating
> > raised to a value greater than, or equal 400.

But all of those qualities (and more) make it less then ideal.

What issue exactly does this patch resolve?

> > Since it's being a tendency among paravirt clocksources to use values
> > around 400, we should declare tsc as even better: So we use 500.

This is the rating inflation I was initially worried about and created
the advisory scale to avoid. If paravirt clocksources are rated too
high, they should be dropped. 

I strongly disagree that the TSC is a "perfect" clocksource, and I think
its rating is appropriate. 


> > This patch also touches the comments on clocksource.h, which suggests
> > that 499 would be a limit on the rating values.
> > 
> > Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
> 
> Acked-by: Thomas Gleixner <tglx@linutronix.de>

If a better justification can be provided, I might reconsider, but right
now I can't ack this.

thanks
-john

> > ---
> >  arch/x86/kernel/tsc_32.c    |    2 +-
> >  arch/x86/kernel/tsc_64.c    |    2 +-
> >  include/linux/clocksource.h |    2 +-
> >  3 files changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/arch/x86/kernel/tsc_32.c b/arch/x86/kernel/tsc_32.c
> > index 9ebc0da..4d91e59 100644
> > --- a/arch/x86/kernel/tsc_32.c
> > +++ b/arch/x86/kernel/tsc_32.c
> > @@ -280,7 +280,7 @@ static cycle_t read_tsc(void)
> >  
> >  static struct clocksource clocksource_tsc = {
> >  	.name			= "tsc",
> > -	.rating			= 300,
> > +	.rating			= 500,
> >  	.read			= read_tsc,
> >  	.mask			= CLOCKSOURCE_MASK(64),
> >  	.mult			= 0, /* to be set */
> > diff --git a/arch/x86/kernel/tsc_64.c b/arch/x86/kernel/tsc_64.c
> > index 9c70af4..4fd5b1b 100644
> > --- a/arch/x86/kernel/tsc_64.c
> > +++ b/arch/x86/kernel/tsc_64.c
> > @@ -262,7 +262,7 @@ static cycle_t __vsyscall_fn vread_tsc(void)
> >  
> >  static struct clocksource clocksource_tsc = {
> >  	.name			= "tsc",
> > -	.rating			= 300,
> > +	.rating			= 500,
> >  	.read			= read_tsc,
> >  	.mask			= CLOCKSOURCE_MASK(64),
> >  	.shift			= 22,
> > diff --git a/include/linux/clocksource.h b/include/linux/clocksource.h
> > index 107787a..5b0aadd 100644
> > --- a/include/linux/clocksource.h
> > +++ b/include/linux/clocksource.h
> > @@ -39,7 +39,7 @@ struct clocksource;
> >   *				A correct and usable clocksource.
> >   *			300-399: Desired.
> >   *				A reasonably fast and accurate clocksource.
> > - *			400-499: Perfect
> > + *			>= 400 : Perfect
> >   *				The ideal clocksource. A must-use where
> >   *				available.
> >   * @read:		returns a cycle value
> > -- 
> > 1.5.0.6
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 


  parent reply	other threads:[~2007-10-30  1:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 23:10 [PATCH] raise tsc clocksource rating Glauber de Oliveira Costa
2007-10-29 22:17 ` Thomas Gleixner
2007-10-29 22:36   ` Ingo Molnar
2007-10-30  1:26   ` john stultz [this message]
2007-10-30  2:39   ` Rusty Russell
2007-10-30  7:37     ` Ingo Molnar
2007-10-30 10:52       ` Rusty Russell
2007-10-30 12:13       ` Glauber de Oliveira Costa
2007-10-29 22:42 ` Zachary Amsden
2007-10-29 22:45   ` Jeremy Fitzhardinge
2007-10-29 22:48   ` Ingo Molnar
2007-10-29 22:52     ` Jeremy Fitzhardinge
2007-10-29 22:55       ` Ingo Molnar
2007-10-29 23:17         ` Jeremy Fitzhardinge
2007-10-29 23:21           ` Ingo Molnar
2007-10-29 23:33             ` Jeremy Fitzhardinge
2007-10-30  0:45             ` Ian Pratt
2007-10-30  7:19               ` Ingo Molnar
2007-10-29 22:55     ` Zachary Amsden
2007-10-29 23:02       ` Ingo Molnar
2007-10-29 23:13         ` Zachary Amsden
2007-10-29 23:17           ` Ingo Molnar
2007-10-30 12:02           ` Glauber de Oliveira Costa
2007-10-30 17:58             ` Zachary Amsden
2007-10-29 23:24         ` Dan Hecht
2007-10-30  4:24           ` [kvm-devel] " Avi Kivity
2007-10-30  7:14           ` Ingo Molnar
2007-10-30 11:59       ` Glauber de Oliveira Costa
2007-10-30  0:17 ` H. Peter Anvin

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=1193707616.11323.6.camel@localhost \
    --to=johnstul@us.ibm.com \
    --cc=--cc@redhat.com \
    --cc=avi@quramnet.com \
    --cc=gcosta@redhat.com \
    --cc=jeremy@goop.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    --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