Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759002AbdLRPXy (ORCPT ); Mon, 18 Dec 2017 10:23:54 -0500 Received: from mail-lf0-f41.google.com ([209.85.215.41]:45218 "EHLO mail-lf0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758835AbdLRPXs (ORCPT ); Mon, 18 Dec 2017 10:23:48 -0500 X-Google-Smtp-Source: ACJfBotdxlR/x704yI1KVaFOpRxRzAllMTm1JAVSF9Ark8s8c3GME9FJtS1HgbBDcD2GYseXWR2EAodL+MsiGGVtQDk= MIME-Version: 1.0 In-Reply-To: References: <20171218132821.5gqxtwotgxvpqzy7@ukko.fi.intel.com> From: Mathieu Poirier Date: Mon, 18 Dec 2017 08:23:46 -0700 Message-ID: Subject: Re: perf record: regression with latest PT fix To: Adrian Hunter Cc: Alexander Shishkin , Stephane Eranian , Jiri Olsa , LKML , Peter Zijlstra , Arnaldo Carvalho de Melo , Andi Kleen Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1182 Lines: 43 On 18 December 2017 at 07:25, Adrian Hunter wrote: > On 18/12/17 15:28, Alexander Shishkin wrote: >> On Mon, Dec 18, 2017 at 05:03:53AM -0800, Stephane Eranian wrote: >>> Hi, >>> >>> >>> The following patch: >>> >>> f785657b0fbe perf report: Fix regression when decoding Intel-PT traces >> >> Cc'ing Adrian in case he missed the patch. > > Doesn't seem to have much to do with Intel PT, but the patch logic looks wrong: > > ret = perf_evlist__parse_sample_timestamp(evlist, event, ×tamp); > - if (ret) > + if (ret != -1) > return ret; > > Shouldn't that be: > > ret = perf_evlist__parse_sample_timestamp(evlist, event, ×tamp); > - if (ret) > + if (ret && ret != -1) > return ret; Of course! Ingo, how do you want to proceed? Should I send a V3? > > >> >>> is breaking perf report for me. I get no samples reported from perf report >>> when running simple perf record commands: >>> >>> $ perf record -e cycles noploop >>> >>> Reverting the patch fixes the problem. >>> >>> Are you seeing this as well? >> >