From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Sheng Yang <sheng@linux.intel.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org
Subject: Re: Make QEmu HPET disabled by default for KVM?
Date: Thu, 11 Mar 2010 13:56:33 +0200 [thread overview]
Message-ID: <4B98DA71.1000305@redhat.com> (raw)
In-Reply-To: <4B98DA5B.6040200@redhat.com>
On 03/11/2010 01:56 PM, Avi Kivity wrote:
> On 03/11/2010 12:23 PM, Gleb Natapov wrote:
>>>>
>>>> If the problem it due to lost ticks reinjection may solve it, but
>>>> only partially.
>>>> What if IO thread haven't run even once during the time vcpu did clock
>>>> source check? IIRC sometimes we trigger this even with in kernel PIT.
>>> That is true. Reinjection can correct problems in the long term,
>>> but may fail in the short term. 10 ticks is easily short term in a
>>> heavily loaded system.
>>>
>>> How does it happen with kernel PIT? I could understand it if we had
>>> a work item doing the injection, but everything happens either from
>>> hrtimer context or vcpu context.
>>>
>> Do we kick vcpu out of guest mode when hrtimer triggers? I don't see
>> us doing it in
>> __kvm_timer_fn().
>>
>
> We're always running on the same cpu as vcpu 0, so no need.
>
Would be better to do it, though, in case we have migration races.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-11 11:56 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 [this message]
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=4B98DA71.1000305@redhat.com \
--to=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