From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: 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 09:10:38 +0200 [thread overview]
Message-ID: <20100314071038.GC19233@redhat.com> (raw)
In-Reply-To: <4B9C8ACE.4090400@redhat.com>
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)
> >Since one already has to use special timer parameters (-rtc-td-hack,
> >-no-kvm-pit-reinjection), using -no-hpet for problematic Linux
> >guests seems fine?
>
> Depends on how common the problematic ones are. If they're common,
> better to have a generic fix.
>
> --
> error compiling committee.c: too many arguments to function
--
Gleb.
next prev parent reply other threads:[~2010-03-14 7:10 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 [this message]
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=20100314071038.GC19233@redhat.com \
--to=gleb@redhat.com \
--cc=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