public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/6] In kernel PIT patch
Date: Wed, 05 Mar 2008 01:18:54 +0200	[thread overview]
Message-ID: <1204672734.25172.24.camel@localhost.localdomain> (raw)
In-Reply-To: <47CD7038.6000200@codemonkey.ws>


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.

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.

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/

  reply	other threads:[~2008-03-04 23:18 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 [this message]
2008-03-05  0:50     ` Anthony Liguori
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=1204672734.25172.24.camel@localhost.localdomain \
    --to=dor.laor@gmail.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox