From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755525AbdESOeU (ORCPT ); Fri, 19 May 2017 10:34:20 -0400 Received: from mga01.intel.com ([192.55.52.88]:63400 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752553AbdESOeT (ORCPT ); Fri, 19 May 2017 10:34:19 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,364,1491289200"; d="scan'208";a="104523687" Date: Fri, 19 May 2017 07:34:18 -0700 From: Andi Kleen To: Adrian Hunter Cc: Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org Subject: Re: [PATCH 37/37] perf intel-pt: Improve sample timestamp Message-ID: <20170519143418.GC15563@tassilo.jf.intel.com> References: <1495184076-23805-1-git-send-email-adrian.hunter@intel.com> <1495184076-23805-38-git-send-email-adrian.hunter@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1495184076-23805-38-git-send-email-adrian.hunter@intel.com> User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 19, 2017 at 11:54:36AM +0300, Adrian Hunter wrote: > The decoder uses its current timestamp in samples. Usually that is a > timestamp that has already passed, but in some cases it is a timestamp for > a branch that the decoder is walking towards, and consequently hasn't > reached. Improve that situation by using the pkt_state to determine when > to use the current or previous timestamp. Thanks. I ran into this problem a lot. Would be good to mark the clear bug fixes like this with cc stable. -Andi