Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1656508

Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches what libdw sees

From Arnaldo Carvalho de Melo <acme@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches what libdw sees
Date 2017-06-02 21:50 +0200
Message-ID <tO0K6-5re-3@gated-at.bofh.it> (permalink)
References <tNVU5-2oY-3@gated-at.bofh.it> <tNWGv-2XT-35@gated-at.bofh.it> <tNXCx-3wP-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Em Fri, Jun 02, 2017 at 06:21:44PM +0200, Milian Wolff escreveu:
> On Freitag, 2. Juni 2017 17:23:41 CEST Arnaldo Carvalho de Melo wrote:
> > Looks ok, having both implementations matching and the callchains making
> > sense for your workloads is a good way to verify the sanity, thanks.

> > I wonder if we shouldn't somehow script this, i.e. build it with one
> > implementation, generate output from some test workload, build it with
> > the other, second output, diff it, report when not the same.
 
> That does sound like a good idea, but I'm unsure how to do it. Note that many 
> "simple" tests work just fine. Only larger complicated workloads trigger this 
> issue for me.
 
> One potential way to test it would be `perf archive` - i.e. I send you the 
> binaries involved and then we can use perf script diffing to ensure it all 
> works...

Humm, I'm trying to cook up a:

  perf data filter --pid 12345 --perf-data-offset 1234567 --output perf.data.subset

to allow when finding some case like that to get a small subset of a
perf.data file with just the sample we want to get the backtrace from +
the mmaps, etc up to that point.

With that I could keep a repo of interesting perf.data files to have in
my regression tests.

- Arnaldo

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 1/2] perf report: ensure the perf DSO mapping matches what libdw sees Milian Wolff <milian.wolff@kdab.com> - 2017-06-02 16:40 +0200
  [PATCH 2/2] perf report: report module before querying isactivation in dwfl unwind Milian Wolff <milian.wolff@kdab.com> - 2017-06-02 16:40 +0200
    Re: [PATCH 2/2] perf report: report module before querying  isactivation in dwfl unwind Arnaldo Carvalho de Melo <acme@redhat.com> - 2017-06-02 17:30 +0200
      Re: [PATCH 2/2] perf report: report module before querying  isactivation in dwfl unwind Jiri Olsa <jolsa@redhat.com> - 2017-06-05 12:50 +0200
  Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches  what libdw sees Arnaldo Carvalho de Melo <acme@redhat.com> - 2017-06-02 17:30 +0200
    Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches what libdw sees Milian Wolff <milian.wolff@kdab.com> - 2017-06-02 18:30 +0200
      Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches  what libdw sees Arnaldo Carvalho de Melo <acme@kernel.org> - 2017-06-02 21:50 +0200
        Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches what libdw sees Milian Wolff <milian.wolff@kdab.com> - 2017-06-03 13:40 +0200
  Re: [PATCH 1/2] perf report: ensure the perf DSO mapping matches  what libdw sees Jiri Olsa <jolsa@redhat.com> - 2017-06-05 12:50 +0200
  [tip:perf/urgent] perf report: Ensure the perf DSO mapping matches  what libdw sees tip-bot for Milian Wolff <tipbot@zytor.com> - 2017-06-07 18:10 +0200

csiph-web