From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751829AbcBJN55 (ORCPT ); Wed, 10 Feb 2016 08:57:57 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42935 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751596AbcBJN5g (ORCPT ); Wed, 10 Feb 2016 08:57:36 -0500 Subject: Re: [PATCH 4/4] KVM: x86: track actual TSC frequency from the timekeeper struct To: Owen Hofmann References: <1454944711-33022-1-git-send-email-pbonzini@redhat.com> <1454944711-33022-5-git-send-email-pbonzini@redhat.com> Cc: LKML , KVM General , Marcelo Tosatti From: Paolo Bonzini Message-ID: <56BB41CB.8010106@redhat.com> Date: Wed, 10 Feb 2016 14:57:31 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@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