public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: dor.laor@qumranet.com
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	Avi Kivity <avik@qumranet.com>
Subject: Re: windows acpi time drift
Date: Tue, 18 Mar 2008 19:07:55 -0500	[thread overview]
Message-ID: <47E0595B.606@codemonkey.ws> (raw)
In-Reply-To: <1205881756.21936.21.camel@localhost.localdomain>

Dor Laor wrote:
> 2. The other option is to have an accurate userspace timer (userspace
> hrtimer exist >= 2.6.24) and to add interface to pic/apic to queue
> pending irqs by the pit/rtc.
> The pending queue can be a simple atomic counter per irq.
>   

So this may explain why I see no appreciable benefit from using the 
in-kernel PIT verses using the userspace PIT and -tdf.  I'm using a 
2.6.24 host kernel and QEMU by default will use the "unix" time source 
which will use setitimer.  IIUC, itimer will use hrtimers.

So if there isn't an appreciate CPU utilization improvement and there 
isn't an increased accuracy, there won't be an improvement.

Do ya'll see an improvement playing multimedia on a 2.6.24 host with the 
in-kernel PIT?

Regards,

Anthony Liguori

> Note that we also need support for older host kernels.
>
> Before implementing yet another in-kernel device I like to hear
> opinions. 
> Regards,
> Dor.
>
>
> -------------------------------------------------------------------------
> 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/

      parent reply	other threads:[~2008-03-19  0:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 23:09 windows acpi time drift Dor Laor
2008-03-18 23:33 ` Dor Laor
2008-03-18 23:57   ` Anthony Liguori
2008-03-18 23:35 ` Anthony Liguori
2008-03-19  8:19   ` Avi Kivity
2008-03-19 14:09     ` Anthony Liguori
2008-03-19 15:39       ` Avi Kivity
2008-03-19 16:27         ` Dor Laor
2008-03-19 17:45           ` Avi Kivity
2008-03-19  0:07 ` Anthony Liguori [this message]

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=47E0595B.606@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avik@qumranet.com \
    --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