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, Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH 0/6] In kernel PIT patch
Date: Thu, 06 Mar 2008 23:17:16 +0200	[thread overview]
Message-ID: <1204838236.3992.15.camel@localhost.localdomain> (raw)
In-Reply-To: <47D05A82.304@codemonkey.ws>


On Thu, 2008-03-06 at 14:56 -0600, Anthony Liguori wrote:
> Avi Kivity wrote:
> >
> >> The thing I'm trying to get at is a quantitative statement about why 
> >> moving the pit into the kernel is the right thing.  I'll try to give 
> >> the patches a try myself in the next couple of days.  I don't think 
> >> it's obvious that it's the right thing to do without some sort of 
> >> benchmark supporting it.
> >>   
> >
> > Playing a movie is better than any benchmark; it reflects actual user 
> > experience in a real and important use case.  Benchmarks are 
> > substitutes for real use cases, not the goal of the optimization.
> 
> I tried out WinXP with the standard HAL and the in-kernel APIC patches.  
> I did not see any appreciable improvement in multimedia playback (video 
> or audio).  I still get the same amount of jitters.  I've tried with and 
> without -tdf too.
> 
> So far, the smoothest play back I've gotten is using the ACPI HAL.  Can 
> you point to a particular example where you see an improvement?  Perhaps 
> a divx or movie trailer that is better with it than without it?
> 

ACPI HAL should perform good. 
The in kernel PIT should fix time drift on standard HAL when playing
movies (pit freq -> 1000hz) and the host cpu is loaded.
If the host is not loaded you might not see the drift.
Use kernel build or tgz + taskset to load the cpu.

Without the patches in-kernel PIC should time drift and userspace PIC +
-tdf shouldn't.

As for quality, sometimes when time drifts the movies looks smoother but
that's not really the required result.

> 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/

      reply	other threads:[~2008-03-06 21:17 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
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 [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=1204838236.3992.15.camel@localhost.localdomain \
    --to=dor.laor@gmail.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@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