From: Antoine Martin <antoine@nagafix.co.uk>
To: dlaor@redhat.com
Cc: Kent Tong <kent@cpttm.org.mo>, kvm@vger.kernel.org
Subject: Re: recommended clock source
Date: Mon, 03 Aug 2009 16:09:32 +0700 [thread overview]
Message-ID: <4A76A94C.9040304@nagafix.co.uk> (raw)
In-Reply-To: <4A769FCC.9070102@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
>>>>> It seems to be an unsettled issue, but, would any kind soul suggest
>>>>> the current
>>>>> best practice for setting the clock in Ubuntu Linux and Windows guests?
>>>> For Linux the best source clock is the kvm pv clock (exist from 2.6.27
>>>> and above).
> # qemu-system-x86_64 -clock ?
> Available alarm timers, in order of precedence:
> dynticks
> hpet
> rtc
> unix
>
> I see no "pv clock"...
> Which one should I use then?
> Did I miss a ./configure or .config option?
>
>> No, we were talking about different clocks.
>> I was explaining the guest source clock while you wanted some info for
>> the host-qemu clock.
Hah, gotcha. You're talking about the guest kernel as in:
clocksource=[hpet|pit|tsc|acpi_pm|cyclone|scx200_hrt|kvm-clock]
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
kvm-clock
So all good, thanks.
>> You can use the default - dynticks. hpet and rtc might be good if you
>> need a fine grain granularity on older < 2.6.24 host kernels.
(I'm on dynticks)
I guess dynticks reduces context switches on the host, but I still get
hundreds per second on guests that are otherwise idle.
How would I go about finding what makes them tick?
Thanks
Antoine
>
>
> Cheers
> Antoine
>
>>>> For windows, standard acpi HAL uses the rtc clock by default. As long as
>>>> you use the -rtc-td-hack it won't drift.
>>>>
>>>> When the tsc is not stable on the host or the host cpu might get into
>>>> deep sleep state (c2), you better use another source clock in the guest
>>>> - for windows it should be the pmtimer (using the boot.ini).
>>>>
>>>>> Thanks!
>>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREKAAYFAkp2qT0ACgkQGK2zHPGK1rsSRQCfdGzkV8Gu+pTkZcnpXivXKQlt
IrsAmwZAbfLzdyiWckoi80iwqc/k+0uA
=Qt5o
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-08-03 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 1:52 recommended clock source Kent Tong
2009-08-03 7:01 ` Dor Laor
2009-08-03 8:11 ` Antoine Martin
2009-08-03 8:29 ` Dor Laor
2009-08-03 9:09 ` Antoine Martin [this message]
2009-08-03 9:33 ` Dor Laor
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=4A76A94C.9040304@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--cc=dlaor@redhat.com \
--cc=kent@cpttm.org.mo \
--cc=kvm@vger.kernel.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