From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sasha Levin <levinsasha928@gmail.com>,
Richard Weinberger <richard@nod.at>,
penberg@cs.helsinki.fi, kvm@vger.kernel.org, mingo@elte.hu,
asias.hejun@gmail.com
Subject: Re: kvm tools: clock sources for hrtimer
Date: Wed, 9 Nov 2011 20:14:31 +0400 [thread overview]
Message-ID: <20111109161431.GE608@moon> (raw)
In-Reply-To: <20111109160006.GD608@moon>
On Wed, Nov 09, 2011 at 08:00:06PM +0400, Cyrill Gorcunov wrote:
...
> >
> > You'll need CONFIG_KVM_CLOCK.
> >
> > I'm not actually sure how close our implementation is to having tsc
> > working so far, Cyrill knows more about that than me.
> >
>
> We dropped tsc while were debuggin timer interrupts and apic routing
> setup, it might be not needed already. (Still to be fair I'm not sure
> does kvm hypervisor has a control bit set for tsc and cause or not vm-exit).
>
> In short -- you could drop this from command line and tell us how it goes ;)
>
The history shows the following commit
| commit 513fa5b4ccba8f9a2270a4f5262433071456540b
| Author: Pekka Enberg <penberg@cs.helsinki.fi>
| Date: Sun Apr 11 20:55:56 2010 +0300
|
| kvm: Force 'notsc' and 'earlyprintk' kernel parameters
|
| We don't support TSC calibration properly and we want early printk so force
| them as kernel parameters.
|
| Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
and as far as I remember it's because we were stuck at apic calibration,
but now we have an apic from kvm hypervisor so I think it's safe to drop it
now (but still should be tested more widely).
Cyrill
next prev parent reply other threads:[~2011-11-09 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 14:27 kvm tools: clock sources for hrtimer Richard Weinberger
2011-11-09 14:49 ` Sasha Levin
2011-11-09 15:42 ` Richard Weinberger
2011-11-09 15:49 ` Sasha Levin
2011-11-09 16:00 ` Cyrill Gorcunov
2011-11-09 16:14 ` Cyrill Gorcunov [this message]
2011-11-09 18:56 ` Richard Weinberger
2011-11-09 19:13 ` Pekka Enberg
2011-11-09 19:25 ` Cyrill Gorcunov
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=20111109161431.GE608@moon \
--to=gorcunov@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=richard@nod.at \
/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