From: Alexander Graf <alex-r27SGEef+tmzQB+pC5nmwQ@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: Marcelo Tosatti <marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
Alexander Graf <alex-r27SGEef+tmzQB+pC5nmwQ@public.gmane.org>,
kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [RFC] fix VMX TSC synchronicity
Date: Tue, 15 Jan 2008 17:42:31 +0100 [thread overview]
Message-ID: <478CE277.9010109@csgraf.de> (raw)
In-Reply-To: <478CCCA9.2080300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity wrote:
> Alexander Graf wrote:
>
>>>>
>>>>
>>>>
>>>>
>>> What I mean is, right now we present really broken tscs to the guest.
>>> After your patch, we present less-broken tscs (at boot, they will
>>> closely resemble stable tscs). But after the machine idles a bit and
>>> cpufreq takes over, the tscs won't be stable any more.
>>>
>>>
>>>
>>>
>> Why would the TSC break due to cpufreq? This patchset was against VMX,
>> which is only available on current Intel CPUs. All of those guarantee a
>> constant TSC increase at the maximum frequency.
>>
>> Also see the Intel Documentation:
>>
>> Vol. 3 18-37
>>
>> For Pentium 4 processors, Intel Xeon processors (family [0FH], models
>> [03H and higher]); for Intel Core Solo and Intel Core Duo processors
>> (family [06H], model [0EH]); for the Intel Xeon processor 5100 series
>> and Intel Core 2 Duo processors (family [06H], model [0FH]): the
>> time-stamp counter increments at a constant rate. That rate may be set
>> by the maximum core-clock to bus-clock ratio of the processor or may be
>> set by the maximum resolved frequency at which the processor is booted.
>> The maximum resolved frequency may differ from the maximum qualified
>> frequency of the processor, see Section 18.17.5 for more
>> detail.
>> The specific processor configuration determines the behavior. Constant
>> TSC behavior ensures that the duration of each clock tick is uniform and
>> supports the use of the TSC as a wall clock timer even if the processor
>> core changes frequency.
>> This is the architectural behavior moving forward.
>>
>
> Thanks; that's reassuring to know that it will work (at least on Intel).
>
>
If I remember correctly, there was a statement on LKML by AMD which said
that the TSC is completely broken on AMD systems, so you should not use
it there anyway.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-01-15 16:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 20:49 [RFC] fix VMX TSC synchronicity Marcelo Tosatti
2008-01-13 12:19 ` Avi Kivity
[not found] ` <478A01D1.7000402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-14 16:06 ` Marcelo Tosatti
2008-01-14 20:46 ` Marcelo Tosatti
2008-01-15 14:59 ` Avi Kivity
2008-01-15 14:33 ` Avi Kivity
[not found] ` <478CC448.1030901-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-15 14:50 ` Alexander Graf
[not found] ` <478CC819.3040106-r27SGEef+tmzQB+pC5nmwQ@public.gmane.org>
2008-01-15 15:09 ` Avi Kivity
[not found] ` <478CCCA9.2080300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-15 16:42 ` Alexander Graf [this message]
[not found] ` <478CE277.9010109-r27SGEef+tmzQB+pC5nmwQ@public.gmane.org>
2008-01-15 17:46 ` Avi Kivity
[not found] ` <478CF186.5030304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-15 18:29 ` Amit Shah
2008-01-16 5:51 ` Andi Kleen
[not found] ` <p73ir1ul3ls.fsf-KvMlXPVkKihbpigZmTR7Iw@public.gmane.org>
2008-01-16 8:46 ` Avi Kivity
[not found] ` <478DC453.1000404-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-16 13:34 ` Andi Kleen
[not found] ` <478E08E5.2030507@qumranet.com>
[not found] ` <478E08E5.2030507-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-16 13:54 ` Andi Kleen
[not found] ` <20080116135415.GA14664-qrUzlfsMFqo/4alezvVtWx2eb7JE58TQ@public.gmane.org>
2008-01-16 13:56 ` Avi Kivity
2008-01-17 18:43 ` Marcelo Tosatti
2008-01-17 18:56 ` Andi Kleen
2008-01-20 14:59 ` Avi Kivity
2008-05-04 15:40 ` Avi Kivity
2008-05-06 13:55 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-01-12 3:11 Will Trives
2008-01-12 12:28 ` Marcelo Tosatti
2008-01-12 13:48 ` Will Trives
2008-01-12 20:51 ` Avi Kivity
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=478CE277.9010109@csgraf.de \
--to=alex-r27sgeef+tmzqb+pc5nmwq@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=marcelo-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
/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