From: Anthony Liguori <anthony@codemonkey.ws>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/6] In kernel PIT patch
Date: Tue, 04 Mar 2008 22:25:07 -0600 [thread overview]
Message-ID: <47CE20A3.2050908@codemonkey.ws> (raw)
In-Reply-To: <200803051141.15701.sheng.yang@intel.com>
Yang, Sheng wrote:
> On Wednesday 05 March 2008 08:50:24 Anthony Liguori wrote:
>
>> So how do we measure the benefits of an in-kernel PIT?
>>
>
> On the time accuracy side, one typical example is in RHEL5 32E guest, time
> flows very slow compared to the host
> (https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1826080&group_id=180599).
> You can simple using "sleep" to test it. And many people complained it
> before, e,g,
> http://www.mail-archive.com/kvm-devel@lists.sourceforge.net/msg10928.html
> And I have to say the timer problem in current KVM is very serious, and this
> patch can solve this.
>
Okay, then my question is, how much does this patch set improve the
situation?
For instance, the bug report shows some circumstances where:
On IA32e RHEL4 guest with
Realtime 3min
Guest 3min15s
So what is the guest time with an in-kernel PIT? How is this affected
by the various possible -clock options? What I'm looking for is an
example of how much we're improving the situation and some assurance
that this is the only way to solve the problem.
I'm not fundamentally opposed to an in-kernel PIT, I just am trying to
understand the justification.
Regards,
Anthony Liguori
> I think you are most worrying about the regressions. That's why I spent a lot
> of time to solve TSC problem (PAE SMP RHEL5.1 can't boot up). For in kernel
> PIT accelerate the process, the same bug was exposed on PAE SMP RHEL5 with
> the patch. Though I don't think it's a real regression, I have got it done to
> prevent this patch bring any bad effect.
>
> I would do more test to ensure this patch won't break something.
>
-------------------------------------------------------------------------
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-03-05 4:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 10:22 [PATCH 0/6] In kernel PIT patch Yang, Sheng
2008-03-04 15:52 ` Anthony Liguori
2008-03-04 23:18 ` Dor Laor
2008-03-05 0:50 ` Anthony Liguori
2008-03-05 3:41 ` Yang, Sheng
2008-03-05 4:25 ` Anthony Liguori [this message]
2008-03-05 5:18 ` Yang, Sheng
2008-03-05 10:14 ` Dor Laor
2008-03-05 14:58 ` Anthony Liguori
2008-03-05 17:30 ` Avi Kivity
2008-03-05 22:40 ` Dor Laor
2008-03-05 23:05 ` Anthony Liguori
2008-03-05 23:24 ` Dor Laor
2008-03-06 20:56 ` Anthony Liguori
2008-03-06 21:17 ` 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=47CE20A3.2050908@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kvm-devel@lists.sourceforge.net \
--cc=sheng.yang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox