From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: A testing for KVM
Date: Thu, 21 Jun 2007 12:01:26 +0300 [thread overview]
Message-ID: <467A3E66.4090406@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A01A562AD-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Dong, Eddie wrote:
> In Xen, we virtualize TSC too to make sure the guest TSC time is
> synchronized with
> guest PIT time, so guest can see an accurate virtual time. (refer my
> presentation
> doc on Xen September summit 06.) It is good but time to time
> we see bugs due to the complicated time virtualization mechanism. As far
> as I know,
> Vmware doesn't solve this problem either, it depends on guest
> application to sync
> guest time with real time (network or host).
>
>
Do you mean that rdtsc is trapped? Or that you play with TSC_OFFSET so
that time is smoother?
> We can use PV time of linux, another way is to persuade community to
> give up
> the cross reference of PIT and TSC to give up picking the lost ticks
> given that
> today's OS is smart enough and won't disable IRQ for that long time
> before
> another PIT expires (1-4ms), so those kind of picking up lost ticks is
> quit
> unnecessary, especially for X86-64 (faster processor).
>
> Another big issue is that guest Linux will eventually fail back to PIT
> time source after
> hundreds of "lost ticks" and thus give up TSC time source. This is OK
> for normal application
> but dead set for database server where gettimeofday is frequently used.
> We saw
> 30-40% performance degradation due to this only. (gettimeofday will
> read port 40
> multiple times which is extremely slow under virtualization).
>
> I will ask Jun, Avi to bring this issue to virtualization mini summit to
> persuade
> communitty to do some changes in guest timer IRQ handler.
>
For newer kernels, we can supply a paravirt clocksource (as in Anthony's
patchset) which will remove the need for changing the bare hardware
time code.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-21 9:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 8:37 A testing for KVM Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77AA3EEA0-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-06-13 8:48 ` Avi Kivity
[not found] ` <466FAF56.4070802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-13 10:16 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A0198452F-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-06-13 10:58 ` Avi Kivity
2007-06-13 11:02 ` Gregory Haskins
[not found] ` <1181732578.26394.9.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-06-13 11:41 ` Dor Laor
2007-06-21 3:23 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01A562AD-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-06-21 9:01 ` Avi Kivity [this message]
[not found] ` <467A3E66.4090406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-21 9:09 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01A56502-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-06-21 9:28 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2007-06-21 5:12 Dong, Eddie
2007-06-21 11:06 Gregory Haskins
[not found] ` <467A23890200005A000262B7-Igcdv/6uVdMHoYOw/+koYqIwWpluYiW7@public.gmane.org>
2007-06-21 12:41 ` Dong, Eddie
2007-06-21 12:50 Gregory Haskins
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=467A3E66.4090406@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 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.