From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 4/4] KVM: x86: track actual TSC frequency from the
 timekeeper struct
Date: Wed, 10 Feb 2016 14:57:31 +0100
Message-ID: <56BB41CB.8010106@redhat.com>
References: <1454944711-33022-1-git-send-email-pbonzini@redhat.com>
 <1454944711-33022-5-git-send-email-pbonzini@redhat.com>
 <CANqFzA5HtR3JJH3Wh2T_0gmSGEco30HDNuYWSc6NfeAUp=mK6g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: LKML <linux-kernel@vger.kernel.org>,
	KVM General <kvm@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>
To: Owen Hofmann <osh@google.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <CANqFzA5HtR3JJH3Wh2T_0gmSGEco30HDNuYWSc6NfeAUp=mK6g@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org



On 09/02/2016 19:41, Owen Hofmann wrote:
> Hi,
> Should this patch change the condition in pvclock_gtod_notify?
> Currently it looks like we'll only request a masterclock update when
> tsc is no longer a good clocksource.

Yes, you're right.

Paolo