public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: 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:00:06 +0400	[thread overview]
Message-ID: <20111109160006.GD608@moon> (raw)
In-Reply-To: <1320853793.31056.75.camel@lappy>

On Wed, Nov 09, 2011 at 05:49:53PM +0200, Sasha Levin wrote:
> On Wed, 2011-11-09 at 17:42 +0200, Richard Weinberger wrote:
> > On Wed, 09 Nov 2011 16:49:51 +0200, Sasha Levin
> > <levinsasha928@gmail.com> wrote:
> > > We'll do kvm_clock as well if you compile it in the kernel.
> > 
> > CONFIG_HIGH_RES_TIMERS is on both host and guest kernels enabled.
> > BTW: Why adds the kvm tool "notsc" to the guest's kernel command line?
> 
> 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 ;)

	Cyrill

  reply	other threads:[~2011-11-09 16:00 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 [this message]
2011-11-09 16:14         ` Cyrill Gorcunov
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=20111109160006.GD608@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