From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: What time is it kvm-clock?
Date: Wed, 24 Feb 2016 00:59:14 -0300
Message-ID: <20160224035913.GB6681@amt.cnet>
References: <CANqFzA5VCQYZ6dYBjz=hbBotwe0S_4cKgxGiK9YU8Ei9G7DYng@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: KVM General <kvm@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Andy Lutomirski <luto@amacapital.net>,
	Peter Hornyack <peterhornyack@google.com>
To: Owen Hofmann <osh@google.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:37998 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756329AbcBXD7c (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 23 Feb 2016 22:59:32 -0500
Content-Disposition: inline
In-Reply-To: <CANqFzA5VCQYZ6dYBjz=hbBotwe0S_4cKgxGiK9YU8Ei9G7DYng@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Tue, Feb 23, 2016 at 06:31:59PM -0800, Owen Hofmann wrote:
> Specifically, what underlying source of time should be exposed through
> kvm-clock and other paravirtual ABIs like the HyperV reference tsc
> page?  Recently a couple of threads on kvm-list, along with attempts
> to produce reliable behavior from kvm-clock 

Please report findings if you find issues in kvm-clock. "unreliable
behavior" ?