public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: Make QEmu HPET disabled by default for KVM?
Date: Thu, 11 Mar 2010 10:28:12 +0200	[thread overview]
Message-ID: <4B98A99C.8020909@redhat.com> (raw)
In-Reply-To: <201003111623.58755.sheng@linux.intel.com>

On 03/11/2010 10:23 AM, Sheng Yang wrote:
>>> I have kept --no-hpet in my setup for
>>> months...
>>>        
>> Any details about the problems?  HPET is important to some guests.
>>
>>      
> Seems like HPET reaction is too slow to satisfy some guests(for it would
> replace PIT).
>
> Here is the thread last time.
>
> http://thread.gmane.org/gmane.comp.emulators.kvm.devel/44899
>
>    

Thanks.  We can address this in three ways: first, adjust the guest not 
to do timing related tests when virtualized (since no matter what we do, 
the tests may fail).  Second, I think we should implement userspace ack 
notifiers (similar to tpr access notifiers already present).  Third, we 
can implement a kernel hpet, which, after we solve the zillion bug it 
introduces, will also give a nice performance improvement for hpet 
intensive workloads.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-03-11  8:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  7:52 Make QEmu HPET disabled by default for KVM? Sheng Yang
2010-03-11  7:58 ` Avi Kivity
2010-03-11  8:23   ` Sheng Yang
2010-03-11  8:28     ` Avi Kivity [this message]
2010-03-11  8:31       ` Gleb Natapov
2010-03-11  8:36         ` Avi Kivity
2010-03-11  8:38         ` Sheng Yang
2010-03-11  8:42           ` Gleb Natapov
2010-03-11  8:46             ` Avi Kivity
2010-03-11 10:23               ` Gleb Natapov
2010-03-11 11:56                 ` Avi Kivity
2010-03-11 11:56                   ` Avi Kivity
2010-03-11 19:08   ` Marcelo Tosatti
2010-03-14  7:05     ` Avi Kivity
2010-03-14  7:10       ` Gleb Natapov
2010-03-14 10:23         ` Dor Laor
2010-03-14 10:27           ` Avi Kivity
2010-03-14 12:51             ` 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=4B98A99C.8020909@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=sheng@linux.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