kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
	"Marcelo Tosatti" <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: invtsc + migration + TSC scaling
Date: Mon, 17 Oct 2016 19:11:01 -0200	[thread overview]
Message-ID: <20161017211101.GD3275@thinpad.lan.raisama.net> (raw)
In-Reply-To: <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com>

On Mon, Oct 17, 2016 at 06:24:38PM +0200, Paolo Bonzini wrote:
> On 17/10/2016 16:50, Radim Krčmář wrote:
> > 2016-10-17 07:47-0200, Marcelo Tosatti:
[...]
> >> since Linux guests use kvmclock and Windows guests use Hyper-V
> >> enlightenment, it should be fine to disable 2).
> 
> ... and 1 too.
> 
> We should also blacklist the TSC deadline timer when invtsc is not
> available.

You mean on the guest-side? On the host side, it would make
existing VMs refuse to run.

-- 
Eduardo

  reply	other threads:[~2016-10-17 21:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 21:20 invtsc + migration + TSC scaling Eduardo Habkost
2016-10-17  9:47 ` Marcelo Tosatti
2016-10-17 14:50   ` Radim Krčmář
2016-10-17 16:24     ` Paolo Bonzini
2016-10-17 21:11       ` Eduardo Habkost [this message]
2016-10-17 23:58         ` Marcelo Tosatti
2016-10-18 13:41           ` Paolo Bonzini
2016-10-18 17:09             ` Marcelo Tosatti
2016-10-18 20:52               ` Radim Krčmář
2016-10-18 21:05                 ` Eduardo Habkost
2016-10-19 13:27                   ` Radim Krčmář
2016-10-19 13:55                     ` Eduardo Habkost
2016-10-19 15:42                       ` Radim Krčmář
2016-10-19 17:42                         ` Eduardo Habkost
2016-10-18 13:48           ` Radim Krčmář
2016-10-18 13:36       ` Radim Krčmář
2016-10-18 13:38         ` Radim Krčmář
2016-10-17 17:20     ` Marcelo Tosatti
2016-10-18 13:27       ` Radim Krčmář
2016-10-18  9:04     ` [Qemu-devel] " Dr. David Alan Gilbert

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=20161017211101.GD3275@thinpad.lan.raisama.net \
    --to=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@redhat.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;
as well as URLs for NNTP newsgroup(s).