From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: invtsc + migration + TSC scaling
Date: Mon, 17 Oct 2016 19:11:01 -0200
Message-ID: <20161017211101.GD3275@thinpad.lan.raisama.net>
References: <20161014212031.GQ3275@thinpad.lan.raisama.net>
 <20161017094708.GB31691@amt.cnet>
 <20161017145008.GA2307@potion>
 <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cc: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>,
        Marcelo Tosatti <mtosatti@redhat.com>, qemu-devel@nongnu.org,
        kvm@vger.kernel.org
To: Paolo Bonzini <pbonzini@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:45748 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S936198AbcJQVLI (ORCPT <rfc822;kvm@vger.kernel.org>);
        Mon, 17 Oct 2016 17:11:08 -0400
Content-Disposition: inline
In-Reply-To: <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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