From: Glauber de Oliveira Costa <gcosta@redhat.com>
To: Zachary Amsden <zach@vmware.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
rusty@rustcorp.com.au, jeremy@goop.org, --cc@redhat.com,
avi@quramnet.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: Tue, 30 Oct 2007 09:59:42 -0200 [thread overview]
Message-ID: <47271CAE.8000907@redhat.com> (raw)
In-Reply-To: <1193698505.9793.90.camel@bodhitayantram.eng.vmware.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zachary Amsden escreveu:
> On Mon, 2007-10-29 at 23:48 +0100, Ingo Molnar wrote:
>> * Zachary Amsden <zach@vmware.com> wrote:
>
>> if it's inaccurate why are you exposing it to the guest then? Native
>> only uses the TSC if it's safe and accurate to do so.
>
> Not every guest support paravirt, but for correctness, all guests
> require TSC, which must be exposed all the way up to userspace, no
> matter what the efficiency or accuracy may be.
>
> Zach
>
However, with such accuracy, it will fail the tsc clocksources tests. If
it passes, it'a good clocksource to use.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iD8DBQFHJxyujYI8LaFUWXMRAhI5AKCDl/O7iA3TdtpvElVg8NoSDVfKpgCeNvz3
ZEZDMxg8T7FA2R+5cgH/uKI=
=8qSH
-----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID (diff)
From: Glauber de Oliveira Costa <gcosta-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
Cc: jeremy-TSDbQ3PG+2Y@public.gmane.org,
avi-i/T1Zxg06OZWk0Htik3J/w@public.gmane.org,
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Dan Hecht <dhecht-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Glauber de Oliveira Costa
<glauber-aMxvdZfKFXomYvmMESoHnA@public.gmane.org>,
--cc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Garrett Smith <garrett-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] raise tsc clocksource rating
Date: Tue, 30 Oct 2007 09:59:42 -0200 [thread overview]
Message-ID: <47271CAE.8000907@redhat.com> (raw)
In-Reply-To: <1193698505.9793.90.camel-cxY/u30q8FloTgUnLF1by8fTvwmfpRNyZeezCHUQhQ4@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zachary Amsden escreveu:
> On Mon, 2007-10-29 at 23:48 +0100, Ingo Molnar wrote:
>> * Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org> wrote:
>
>> if it's inaccurate why are you exposing it to the guest then? Native
>> only uses the TSC if it's safe and accurate to do so.
>
> Not every guest support paravirt, but for correctness, all guests
> require TSC, which must be exposed all the way up to userspace, no
> matter what the efficiency or accuracy may be.
>
> Zach
>
However, with such accuracy, it will fail the tsc clocksources tests. If
it passes, it'a good clocksource to use.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Remi - http://enigmail.mozdev.org
iD8DBQFHJxyujYI8LaFUWXMRAhI5AKCDl/O7iA3TdtpvElVg8NoSDVfKpgCeNvz3
ZEZDMxg8T7FA2R+5cgH/uKI=
=8qSH
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-30 11:59 UTC|newest]
Thread overview: 52+ 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 23:10 ` Glauber de Oliveira Costa
2007-10-29 22:17 ` Thomas Gleixner
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 2:39 ` Rusty Russell
2007-10-30 7:37 ` Ingo Molnar
2007-10-30 7:37 ` Ingo Molnar
2007-10-30 10:52 ` Rusty Russell
2007-10-30 10:52 ` Rusty Russell
2007-10-30 12:13 ` Glauber de Oliveira Costa
2007-10-30 12:13 ` Glauber de Oliveira Costa
2007-10-29 22:42 ` Zachary Amsden
2007-10-29 22:42 ` Zachary Amsden
2007-10-29 22:45 ` Jeremy Fitzhardinge
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:52 ` Jeremy Fitzhardinge
2007-10-29 22:55 ` Ingo Molnar
2007-10-29 23:17 ` Jeremy Fitzhardinge
2007-10-29 23:17 ` Jeremy Fitzhardinge
2007-10-29 23:21 ` Ingo Molnar
2007-10-29 23:21 ` Ingo Molnar
2007-10-29 23:33 ` Jeremy Fitzhardinge
2007-10-29 23:33 ` Jeremy Fitzhardinge
2007-10-30 0:45 ` Ian Pratt
2007-10-30 0:45 ` Ian Pratt
2007-10-30 7:19 ` Ingo Molnar
2007-10-30 7:19 ` Ingo Molnar
2007-10-29 22:55 ` Zachary Amsden
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-29 23:17 ` Ingo Molnar
2007-10-30 12:02 ` Glauber de Oliveira Costa
2007-10-30 12:02 ` Glauber de Oliveira Costa
2007-10-30 17:58 ` Zachary Amsden
2007-10-30 17:58 ` Zachary Amsden
2007-10-29 23:24 ` Dan Hecht
2007-10-29 23:24 ` Dan Hecht
2007-10-30 4:24 ` [kvm-devel] " Avi Kivity
2007-10-30 4:24 ` Avi Kivity
2007-10-30 7:14 ` Ingo Molnar
2007-10-30 7:14 ` Ingo Molnar
2007-10-30 11:59 ` Glauber de Oliveira Costa [this message]
2007-10-30 11:59 ` Glauber de Oliveira Costa
2007-10-30 0:17 ` H. Peter Anvin
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=47271CAE.8000907@redhat.com \
--to=gcosta@redhat.com \
--cc=--cc@redhat.com \
--cc=avi@quramnet.com \
--cc=dhecht@vmware.com \
--cc=garrett@vmware.com \
--cc=glauber@t60.localdomain \
--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 \
--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 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.