From: Anthony Liguori <anthony@codemonkey.ws>
To: dor.laor@qumranet.com
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/6] In kernel PIT patch
Date: Tue, 04 Mar 2008 18:50:24 -0600 [thread overview]
Message-ID: <47CDEE50.3060206@codemonkey.ws> (raw)
In-Reply-To: <1204672734.25172.24.camel@localhost.localdomain>
Dor Laor wrote:
> On Tue, 2008-03-04 at 09:52 -0600, Anthony Liguori wrote:
>
>> Yang, Sheng wrote:
>>
>>> Hi
>>>
>>> Here is the last in-kernel PIT patch for KVM. The mainly change from last
>>> version is the supporting to save/restore. I also tested live migration.
>>>
>>> The other modifies including some date structure changed to be better for
>>> supporting the save/restore. I moved the PIT timer to outside of channel
>>> structure, which explicitly means only one channel (channel 0) would trigger
>>> it.
>>>
>>> After fix TSC problem on SMP PAE RHEL5/5.1 guest, now the patch works well
>>> without any modify of kernel parameter.
>>>
>>>
>> How are you measuring the improvements from an in-kernel PIT? From your
>> mails, you're claiming it increases the timer accuracy. How are you
>> measuring it and how much does it improve it?
>>
>>
>
> It's also a functionality addition: userspace pit & pic combination
> needed to use -tdf option (time drift fix). The tdf took care of pending
> pit irqs and tried to make the guest ack the right number of irqs the
> pit was configured.
>
I thought there was some discussion about whether -tdf was every useful
in practice?
> Once we switched to the default in-kernel pic, the userspace pit
> couldn't get the acks from the pit.
> One can see the effect when running multiple guests (windows, standard
> HAL) playing video, the time slows down.
>
Okay, that makes sense. So have you done any tests to confirm this? We
suffered through a fair number of regressions when we moved to an
in-kernel APIC. Before moving another big chunk of code in the kernel
and going through possible regressions, I want to make sure we have a
measurable argument that it's the right thing to do.
So how do we measure the benefits of an in-kernel PIT?
Regards,
Anthony Liguori
> This patch set has a pending counter and takes care for it too.
>
>
>> Do you expect an overall performance improvement from this or is it
>> simply about improving timer accuracy?
>>
>>
>
> It will probably help older kernels with slow HZ run faster HZ guests.
> Without CONFIG_DYNTICK the guests behaved jumpy because of that.
>
>
>> Regards,
>>
>> Anthony Liguori
>>
>>
>>
>> -------------------------------------------------------------------------
>> 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/
>> _______________________________________________
>> kvm-devel mailing list
>> kvm-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>>
>
>
-------------------------------------------------------------------------
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 0:50 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 [this message]
2008-03-05 3:41 ` Yang, Sheng
2008-03-05 4:25 ` Anthony Liguori
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=47CDEE50.3060206@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=dor.laor@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
/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.