From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751301AbdAWSo1 (ORCPT ); Mon, 23 Jan 2017 13:44:27 -0500 Received: from mail-wm0-f65.google.com ([74.125.82.65]:36573 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750742AbdAWSoZ (ORCPT ); Mon, 23 Jan 2017 13:44:25 -0500 Date: Mon, 23 Jan 2017 19:44:15 +0100 From: Richard Cochran To: Marcelo Tosatti Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Paolo Bonzini , Radim Krcmar , Miroslav Lichvar Subject: Re: [patch 4/5] PTP: add PTP_SYS_OFFSET emulation via cross timestamps infrastructure Message-ID: <20170123184415.GA2158@localhost.localdomain> References: <20170120122025.665985919@redhat.com> <20170120122503.746158230@redhat.com> <20170120202502.GA10368@localhost.localdomain> <20170123131913.GA28104@amt.cnet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170123131913.GA28104@amt.cnet> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 23, 2017 at 11:19:17AM -0200, Marcelo Tosatti wrote: > This is needed to generate the PTP_SYS_OFFSET data: a table with read > from realtime clock, read from device clock, read from realtime clock, > ... : > > time -> > device clock | |sample2| |sample4| |sample6| ... > ------------------------------------------------------------- > realtime clock |sample1| |sample3| |sample5| Here "realtime clock" is CLOCK_REALTIME on the guest, and "device clock" is CLOCK_REALTIME on the host? > Where sampleN is the read of the respective clock. > > From the following PTP_SYS_OFFSET_PRECISE data: > > device clock |sample1P,deviceclock| |sample2P,deviceclock| > ------------------------------------------------------------- > realtime clock |sample1P,realtimeclock| |sample2P,realtimeclock| Are |sample1P,deviceclock| and |sample1P,realtimeclock| taken at the same instant in time? If not, then calling that PTP_SYS_OFFSET_PRECISE is misleading. Still don't get what you are doing here... Thanks, Richard