From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [patch 5/5] PTP: add kvm PTP driver Date: Fri, 20 Jan 2017 17:10:33 -0200 Message-ID: <20170120191030.GA1942@amt.cnet> References: <20170120122025.665985919@redhat.com> <20170120122503.842086637@redhat.com> <20170120141255.GA1365@potion> <20170120150025.GB6350@amt.cnet> <20170120180848.GG6291@potion> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Paolo Bonzini , Richard Cochran , Miroslav Lichvar To: Radim Krcmar Return-path: Content-Disposition: inline In-Reply-To: <20170120180848.GG6291@potion> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Fri, Jan 20, 2017 at 07:08:49PM +0100, Radim Krcmar wrote: > 2017-01-20 13:00-0200, Marcelo Tosatti: > > On Fri, Jan 20, 2017 at 03:12:56PM +0100, Radim Krcmar wrote: > >> 2017-01-20 10:20-0200, Marcelo Tosatti: > >> > + do { > >> > + /* > >> > + * We are measuring the delay between > >> > + * kvm_hypercall and rdtsc using TSC, > >> > + * and converting that delta to > >> > + * tsc_to_system_mul and tsc_shift > >> > + * So any changes to tsc_to_system_mul > >> > + * and tsc_shift in this region > >> > + * invalidate the measurement. > >> > + */ > >> > + version = pvclock_read_begin(src); > >> > + > >> > + ret = kvm_hypercall2(KVM_HC_CLOCK_PAIRING, > >> > + clock_off_gpa, > >> > + KVM_CLOCK_PAIRING_WALLCLOCK); > >> > + if (ret != 0) { > >> > + pr_err("clock offset hypercall ret %lu\n", ret); > >> > + spin_unlock(&kvm_ptp_lock); > >> > + preempt_enable_notrace(); > >> > + return -EOPNOTSUPP; > >> > + } > >> > + > >> > + tspec.tv_sec = clock_off.sec; > >> > + tspec.tv_nsec = clock_off.nsec; > >> > + ret = __pvclock_read_cycles(src, clock_off.tsc); > >> > + flags = src->flags; > >> > + } while (pvclock_read_retry(src, version)); > >> > + > >> > + preempt_enable_notrace(); > >> > + > >> > + system_counter->cycles = ret; > >> > + system_counter->cs = get_kvmclock_cs(); > >> > >> Can't we use clocksource_tsc and just pass the tsc without kvmclock in > >> the middle? > > > > No, it has to be the kvmclock value. > > What happens if the guest switches from kvmclock to tsc? The ioctl will return -ENODEV. >>From get_device_system_crosststamp function: /* * Verify that the clocksource associated with the * captured * system counter value is the same as the currently * installed * timekeeper clocksource */ if (tk->tkr_mono.clock != system_counterval.cs) return -ENODEV;