From: Ingo Molnar <mingo@elte.hu>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: kvm & dyntick
Date: Sun, 14 Jan 2007 09:39:54 +0100 [thread overview]
Message-ID: <20070114083954.GB2913@elte.hu> (raw)
In-Reply-To: <45A7BF9F.5090508@qumranet.com>
* Avi Kivity <avi@qumranet.com> wrote:
> >( for this to work on my system i have added a 'hyper' clocksource
> > hypercall API for KVM guests to use - this is needed instead of the
> > running-to-slowly TSC. )
> >
>
> What's the problem with the TSC? The only issue I'm aware of is that
> the tsc might go backwards if the vcpu is migrated to another host cpu
> (easily fixed).
this is not a problem of KVM - this is a problem of this laptop: its TSC
stops when going idle. So the TSC is fundamentally unusable for reliable
timekeeping - and qemu doesnt offer pmtimer emulation to fall back to,
so the dyntick kernel refused to go high-res under KVM. Once i added the
hyper clocksource to fall back to, it could utilize the PIT and the
lapic for clock-events.
Ingo
next prev parent reply other threads:[~2007-01-14 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 16:08 kvm & dyntick Avi Kivity
[not found] ` <45A66106.5030608-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-12 5:34 ` Rik van Riel
2007-01-12 6:20 ` Ingo Molnar
[not found] ` <20070112062006.GA32714-X9Un+BFzKDI@public.gmane.org>
2007-01-12 10:19 ` Ingo Molnar
[not found] ` <20070112101931.GA11635-X9Un+BFzKDI@public.gmane.org>
2007-01-12 17:04 ` Avi Kivity
2007-01-14 8:39 ` Ingo Molnar [this message]
2007-01-12 23:25 ` [kvm-devel] " Dor Laor
2007-01-12 23:39 ` Thomas Gleixner
2007-01-14 8:51 ` Ingo Molnar
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=20070114083954.GB2913@elte.hu \
--to=mingo@elte.hu \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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