From: Dor Laor <dlaor@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Sheng Yang <sheng@linux.intel.com>,
kvm@vger.kernel.org
Subject: Re: Make QEmu HPET disabled by default for KVM?
Date: Sun, 14 Mar 2010 14:51:08 +0200 [thread overview]
Message-ID: <4B9CDBBC.3020900@redhat.com> (raw)
In-Reply-To: <4B9CB9F8.6010205@redhat.com>
On 03/14/2010 12:27 PM, Avi Kivity wrote:
> On 03/14/2010 12:23 PM, Dor Laor wrote:
>> On 03/14/2010 09:10 AM, Gleb Natapov wrote:
>>> On Sun, Mar 14, 2010 at 09:05:50AM +0200, Avi Kivity wrote:
>>>> On 03/11/2010 09:08 PM, Marcelo Tosatti wrote:
>>>>>
>>>>>>
>>>>>>> I have kept --no-hpet in my setup for
>>>>>>> months...
>>>>>> Any details about the problems? HPET is important to some guests.
>>>>> As Gleb mentioned in the other thread, reinjection will introduce
>>>>> another set of problems.
>>>>>
>>>>> Ideally all this timer related problems should be fixed by correlating
>>>>> timer interrupts and time source reads.
>>>>
>>>> This still needs reinjection (or slewing of the timer frequency).
>>>> Correlation doesn't fix drift.
>>>>
>>> But only when all time sources are synchronised and correlated with
>>> interrupts we can slew time frequency without guest noticing (and only
>>> if guest disables NTP)
>>
>> In the mean time we should definitely disable hpet by default.
>
> Definitely not. Windows needs it. Some pre-kvmclock Linux may also work
> with it.
>
> Without hpet, there is no fast high resolution timer in the system.
It's all depends on how hard would it be to re-inject to windows guest.
We still need to fix the win2k3 64 bit and win2k8 64 bit (and not win7
as I told initially) since the irq is broadcasted to all the vcpus and
we do not track who acknowledged the irq.
>
>> Besides this we need to fully virtualize the tsc, fix win7 64bit rtc
>> time drift and some pvclock potential issues. Before we add new timer,
>> better fix existing ones.
>>
>> What about creating a pv time keeping device that will be aware of
>> lost ticks and host wall clock time? It's similar to hyper-v
>> enlightenment virt timers.
>
> That's kvmclock.
>
I meant a device that can be used to generate timeouts. We do use today
pit/rtc along with kvmclock time source but it's not perfect and
probably the same for hpet. This is why I tough that a pv device will be
beneficial.
prev parent reply other threads:[~2010-03-14 12:50 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
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 [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=4B9CDBBC.3020900@redhat.com \
--to=dlaor@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@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