From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [patch 3/3] PTP: add kvm PTP driver
Date: Mon, 16 Jan 2017 17:36:55 -0200
Message-ID: <20170116193655.GA7649@amt.cnet>
References: <20170113120131.086634482@redhat.com>
 <20170113120319.777765254@redhat.com>
 <20170113155657.GD22440@potion>
 <20170113174014.GA9310@amt.cnet>
 <20170116162653.GA32097@potion>
 <20170116165411.GA2386@potion>
 <20170116170827.GB2501@amt.cnet>
 <20170116172758.GB31452@potion>
 <20170116173909.GA4639@amt.cnet>
 <20170116180147.GD31452@potion>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
        Paolo Bonzini <pbonzini@redhat.com>,
        Richard Cochran <richardcochran@gmail.com>,
        Miroslav Lichvar <mlichvar@redhat.com>
To: Radim Krcmar <rkrcmar@redhat.com>,
        Miroslav Lichvar <mlichvar@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20170116180147.GD31452@potion>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Mon, Jan 16, 2017 at 07:01:48PM +0100, Radim Krcmar wrote:
> > Sorry the clock difference is 10ns now. So the guest clock is off by _10 ns_ 
> > of the host clock.
> 
> That is pretty good.

Yes.

> > You are suggesting to use getcrosststamp instead, to drop the (rdtsc() -
> > guest_tsc) part ?
> 
> Yes, it results in simpler code, doesn't create dependency on the
> dreaded kvmclock, and is the best we can currently do wrt. precision.

Sorry, unless i am misunderstanding how this works, it'll get the guest clock
2us behind, which is something not wanted.

Miroslav, if ->gettime64 returns the host realtime at 2us in the past, 
this means Chrony will sync the guest clock to

host realtime - 2us

Is that correct?