From: "Yang, Sheng" <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Yves Dorfsman <yves-Qq95MN99UUsAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: keeping time
Date: Thu, 27 Dec 2007 15:05:06 +0800 [thread overview]
Message-ID: <200712271505.06987.sheng.yang@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712262349310.20371@nyksae>
On Thursday 27 December 2007 14:51:06 Yves Dorfsman wrote:
> On Thu, 27 Dec 2007, Yang, Sheng wrote:
> > What's your guest kernel version?
>
> 2.6.22
>
> > When I debug my in kernel PIT(not sent yet, though kept for months), I
> > found the kernel version have something to do with the timer accuracy. On
> > my limited test, the kernel 2.6.18, 2.6.20, 2.6.22 with default kernel
> > parameters works well with my PIT patch. But for kernel 2.6.9, I have to
> > use "clock=pit", otherwise the timer is much faster.
>
> I have added clock=pit, but it does not help. Do you need a specific patch
> for this, or do all kernels accept it ?
Oh, this is a kernel parameter, but currently:
1. The latest kernel using "clocksource=" instead of "clock=". You can check
the Documentation/kernel-parameters.txt
2. I haven't sent out the in-kernel PIT patch... At present, KVM still using
PIT from userspace/QEMU.
I guesses you are under heavy workload? For "sleep" in bash seems ok on 2.6.22
(x86_64, using RHEL5 as guest distro).
>
>
> Yves.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
--
Thanks
Yang, Sheng
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-12-27 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 14:35 keeping time Yves Dorfsman
2007-12-26 14:39 ` Izik Eidus
2007-12-26 14:51 ` Avi Kivity
[not found] ` <47726A7D.1010103-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-26 17:13 ` Yves Dorfsman
2007-12-26 17:10 ` Izik Eidus
[not found] ` <47728B01.1090603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-26 17:51 ` Yves Dorfsman
2007-12-27 2:28 ` Yang, Sheng
[not found] ` <200712271028.52234.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2007-12-27 6:51 ` Yves Dorfsman
2007-12-27 7:05 ` Yang, Sheng [this message]
2007-12-27 7:19 ` Dong, Eddie
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=200712271505.06987.sheng.yang@intel.com \
--to=sheng.yang-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=yves-Qq95MN99UUsAvxtiuMwx3w@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.