From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"ak@linux.intel.com" <ak@linux.intel.com>,
Vince Weaver <vincent.weaver@maine.edu>,
acme@kernel.org
Subject: Re: [BUG] perf report --pid not reporting correctly
Date: Wed, 21 Sep 2016 18:34:53 +0200 [thread overview]
Message-ID: <20160921163453.GA28844@krava> (raw)
In-Reply-To: <20160921153753.GA2501@redhat.com>
On Wed, Sep 21, 2016 at 12:37:53PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 20, 2016 at 06:29:59PM -0700, Stephane Eranian escreveu:
> > Hi Arnaldo,
> >
> > I ran into an issue trying to use the --pid filtering option of perf report.
> >
> > I do a system-wide collection and then I want to narrow down the
> > reporting to a specific process:
> >
> > $ perf record -a -e cycles:pp sleep 10
> > $ perf report --sort cpu,comm --pid X
> >
> > Where X is a process sampled during the run (easy to catch with perf report -D)
> > If you do it this way, it works, but if you do:
> >
> > $ perf report --sort cpu --pid X
> >
> > Then you get an empty output.
> >
> > I suspect it has to do with the way hist entries are added to the
> > histogram and aggregated. If the first event for a sort criteria is
> > not coming from pid X, it will
> > still be added in the histogram. if pid X aggregates to the same
> > sample criteria, then you will lose the pid information. And then
> > later when you try to apply the filter,
> > it will mark the hist entry as FILTERED because it does not have a matching pid
> > and nothing will be printed.
> > I suspect you want to apply the filtering upfront for pid. It will
> > only add to the histograms matching samples. It changes the
> > percentages you will see. They will
> > only report the breakdown for the pid.
> >
> > I have a quick hack to do upfront filtering which does something as
> > follows but I am not sure this is the correct way of doing this.
> >
> > Let me know what you think.
>
> From a first look I think this makes sense, i.e. we should do the first
> round of filtering, one that trows away stuff, for things in the command
> line, when creating the histogram entries.
>
> Later, as we have now, we can apply further filters for non-collapsed
> fields of hist_entry.
>
> Jiri, Namhyung, are you ok with this?
Stephan is correct with analysis, but I think we need to add both non/filtered
entries in, because we provide that 'F' key for non/filtered counts switch in tui
how about something like below
thanks,
jirka
---
diff --git a/tools/perf/util/hist.c b/tools/perf/util/hist.c
index b02992efb513..659e0357be68 100644
--- a/tools/perf/util/hist.c
+++ b/tools/perf/util/hist.c
@@ -536,6 +536,14 @@ static struct hist_entry *hists__findnew_entry(struct hists *hists,
map__put(he->ms.map);
he->ms.map = map__get(entry->ms.map);
}
+
+ /*
+ * We have at least one entry in which is not
+ * filtered, we want to display the entry.
+ */
+ if (he->filtered && !entry->filtered)
+ he->filtered = 0;
+
goto out;
}
next prev parent reply other threads:[~2016-09-21 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 1:29 [BUG] perf report --pid not reporting correctly Stephane Eranian
2016-09-21 15:37 ` Arnaldo Carvalho de Melo
2016-09-21 16:34 ` Jiri Olsa [this message]
2016-09-21 20:18 ` Stephane Eranian
2016-09-22 1:34 ` Namhyung Kim
2016-09-22 2:22 ` Stephane Eranian
2016-09-22 3:20 ` Namhyung Kim
2016-09-22 13:36 ` Jiri Olsa
2016-09-23 3:31 ` Namhyung Kim
2016-09-22 0:14 ` Namhyung Kim
2016-09-22 14:57 ` Andi Kleen
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=20160921163453.GA28844@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=vincent.weaver@maine.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).