Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751826AbbG2Lss (ORCPT ); Wed, 29 Jul 2015 07:48:48 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:37789 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750803AbbG2Lsq (ORCPT ); Wed, 29 Jul 2015 07:48:46 -0400 Date: Wed, 29 Jul 2015 13:48:41 +0200 From: Richard Cochran To: Peter Zijlstra Cc: Thomas Gleixner , John Stultz , Christopher Hall , Ingo Molnar , Jeff Kirsher , john.ronciak@intel.com, "H. Peter Anvin" , "x86@kernel.org" , lkml , netdev@vger.kernel.org Subject: Re: [PATCH 1/5] Add functions producing system time given a backing counter value Message-ID: <20150729114840.GA16880@localhost.localdomain> References: <1438044416-15588-1-git-send-email-christopher.s.hall@intel.com> <1438044416-15588-2-git-send-email-christopher.s.hall@intel.com> <20150729104944.GM19282@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150729104944.GM19282@twins.programming.kicks-ass.net> 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 Content-Length: 831 Lines: 22 On Wed, Jul 29, 2015 at 12:49:44PM +0200, Peter Zijlstra wrote: > This is still fuzzy, right? The hardware ART timestamp could be from > _before_ the NTP adjust; or the NTP adjust could happen while we do this > conversion and we'll take the retry loop. In the original series, yes. > In both cases, the resulting value is computed using a different slope > than was in effect at the time of the stamp. With the end result being > slightly off from what it should be. In Thomas' patch the get_ts() is meant to read fresh pairs of time stamps from within the loop. Thanks, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/