All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Stephane Eranian <eranian@google.com>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andi Kleen <ak@linux.intel.com>,
	acme@kernel.org
Subject: Re: perf record: regression with latest PT fix
Date: Mon, 18 Dec 2017 14:44:31 -0200	[thread overview]
Message-ID: <20171218164431.GE2777@redhat.com> (raw)
In-Reply-To: <CANLsYkzPHqT-ue=Ew9zy0X1RWfjZD2Wy=2XaD4AmzkxMDotYwg@mail.gmail.com>

Em Mon, Dec 18, 2017 at 08:23:46AM -0700, Mathieu Poirier escreveu:
> On 18 December 2017 at 07:25, Adrian Hunter <adrian.hunter@intel.com> 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, &timestamp);
> > -               if (ret)
> > +               if (ret != -1)
> >                         return ret;
> >
> > Shouldn't that be:
> >
> >                 ret = perf_evlist__parse_sample_timestamp(evlist, event, &timestamp);
> > -               if (ret)
> > +               if (ret && ret != -1)
> >                         return ret;
> 
> Of course!
> 
> Ingo, how do you want to proceed?  Should I send a V3?

Probably, I've run into this as well, as has Ingo, after I reverted it,
things got back working.

Back to vacations... :-)

- Arnaldo
 
> >>> 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?
> >>
> >

      reply	other threads:[~2017-12-18 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 13:03 perf record: regression with latest PT fix Stephane Eranian
     [not found] ` <20171218132821.5gqxtwotgxvpqzy7@ukko.fi.intel.com>
2017-12-18 14:25   ` Adrian Hunter
2017-12-18 15:23     ` Mathieu Poirier
2017-12-18 16:44       ` Arnaldo Carvalho de Melo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171218164431.GE2777@redhat.com \
    --to=acme@redhat.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.