From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Zachary Amsden <zach@vmware.com>,
Glauber de Oliveira Costa <gcosta@redhat.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
rusty@rustcorp.com.au, Avi Kivity <avi@qumranet.com>,
kvm-devel@lists.sourceforge.net,
Glauber de Oliveira Costa <glauber@t60.localdomain>,
Dan Hecht <dhecht@vmware.com>, Garrett Smith <garrett@vmware.com>
Subject: Re: [PATCH] raise tsc clocksource rating
Date: Mon, 29 Oct 2007 16:17:20 -0700 [thread overview]
Message-ID: <47266A00.4040408@goop.org> (raw)
In-Reply-To: <20071029225528.GA31293@elte.hu>
Ingo Molnar wrote:
> that's totally broken then. You cannot create an SMP-safe monotonic
> clocksource via interpolation - native does not do it either. Good thing
> this problem got exposed, it needs to be fixed.
>
Sigh, I don't really want to have this fight again.
I don't really see what point there is in raising the tsc's rating (why
is 300 insufficient again?), but regardless of the value, the Xen
clocksource rating needs to be higher.
J
next prev parent reply other threads:[~2007-10-29 23:17 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
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 [this message]
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=47266A00.4040408@goop.org \
--to=jeremy@goop.org \
--cc=avi@qumranet.com \
--cc=dhecht@vmware.com \
--cc=garrett@vmware.com \
--cc=gcosta@redhat.com \
--cc=glauber@t60.localdomain \
--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 \
--cc=zach@vmware.com \
/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