From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] KVM: x86: fix TSC matching
Date: Fri, 15 Aug 2014 13:54:17 -0300
Message-ID: <20140815165417.GA29279@amt.cnet>
References: <1403595763-2751-1-git-send-email-tgrabiec@cloudius-systems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org
To: Tomasz Grabiec <tgrabiec@cloudius-systems.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:22787 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751631AbaHOQyd (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 15 Aug 2014 12:54:33 -0400
Content-Disposition: inline
In-Reply-To: <1403595763-2751-1-git-send-email-tgrabiec@cloudius-systems.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>


Ping on integration.

On Tue, Jun 24, 2014 at 09:42:43AM +0200, Tomasz Grabiec wrote:
> I've observed kvmclock being marked as unstable on a modern
> single-socket system with a stable TSC and qemu-1.6.2 or qemu-2.0.0.
> 
> The culprit was failure in TSC matching because of overflow of
> kvm_arch::nr_vcpus_matched_tsc in case there were multiple TSC writes
> in a single synchronization cycle.