From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: invtsc + migration + TSC scaling
Date: Tue, 18 Oct 2016 15:41:03 +0200
Message-ID: <74794dbf-a904-54b9-315f-1bc385a959ba@redhat.com>
References: <20161014212031.GQ3275@thinpad.lan.raisama.net>
 <20161017094708.GB31691@amt.cnet> <20161017145008.GA2307@potion>
 <72b8c6b3-f08a-735a-e283-99d0195dcf7d@redhat.com>
 <20161017211101.GD3275@thinpad.lan.raisama.net>
 <20161017235846.GA22657@amt.cnet>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= <rkrcmar@redhat.com>,
        qemu-devel@nongnu.org, kvm@vger.kernel.org
To: Marcelo Tosatti <mtosatti@redhat.com>,
        Eduardo Habkost <ehabkost@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:47528 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1755586AbcJRNlI (ORCPT <rfc822;kvm@vger.kernel.org>);
        Tue, 18 Oct 2016 09:41:08 -0400
In-Reply-To: <20161017235846.GA22657@amt.cnet>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>



On 18/10/2016 01:58, Marcelo Tosatti wrote:
> > We should also blacklist the TSC deadline timer when invtsc is not
> > available.
>
> Actually, a nicer fix would be to check the different 
> frequencies and scale the deadline relative to the difference. 

You cannot know what exactly the guest was thinking when it set the TSC
deadline.  Perhaps it wanted an interrupt when the TSC was exactly
9876543210.

Paolo