From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>
Subject: Re: [PATCHSET 0/5] perf report: Make --stat output more compact
Date: Mon, 26 Apr 2021 09:53:17 -0300 [thread overview]
Message-ID: <YIa3vXJrVwN44mjx@kernel.org> (raw)
In-Reply-To: <20210426043147.GU1401198@tassilo.jf.intel.com>
Em Sun, Apr 25, 2021 at 09:31:47PM -0700, Andi Kleen escreveu:
> > Hmm.. do you want something like this?
> > TOTAL events: 20064
> > MMAP events: 239 ( 1.2%)
> > COMM events: 1518 ( 7.6%)
> > EXIT events: 1 (0.0%)
> > FORK events: 1517 (7.6%)
> > SAMPLE events: 4015 (20.0%)
> > MMAP2 events: 12769 (63.6%)
> Yes that's it.
> Really shows how inefficient perf is for short measurement
> periods.
Brainstorming a bit:
Yeah, I wonder if we could have a new mode where 'perf daemon' collects
the !SAMPLE records and then a 'perf record' would collect just
PERF_RECORD_SAMPLEs, and then 'perf report' would merge things up.
A perf.data file cap for the 'perf daemon' would mean that when a 'perf
report' result looks interesting, one could press a hotkey and generate
a complete perf.data file with the !SAMPLE records needed to have it
self sufficient.
Additionally maybe we could have 'perf daemon' providing a interface to
resolve samples, returning unresolved ones for older stuff.
wdyt?
- Arnaldo
next prev parent reply other threads:[~2021-04-26 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 18:28 [PATCHSET 0/5] perf report: Make --stat output more compact Namhyung Kim
2021-04-23 18:28 ` [PATCH 1/5] perf top: Use evlist->events_stat to count events Namhyung Kim
2021-04-23 18:28 ` [PATCH 2/5] perf hists: Split hists_stats from events_stats Namhyung Kim
2021-04-23 18:28 ` [PATCH 3/5] perf report: Show event sample counts in --stat output Namhyung Kim
2021-04-23 18:28 ` [PATCH 4/5] perf report: Add --skip-empty option to suppress 0 event stat Namhyung Kim
2021-04-23 18:28 ` [PATCH 5/5] perf report: Make --skip-empty as default Namhyung Kim
2021-04-23 18:46 ` [PATCHSET 0/5] perf report: Make --stat output more compact Andi Kleen
2021-04-23 19:00 ` Namhyung Kim
2021-04-23 20:20 ` Andi Kleen
2021-04-25 18:07 ` Namhyung Kim
2021-04-26 4:31 ` Andi Kleen
2021-04-26 12:53 ` Arnaldo Carvalho de Melo [this message]
2021-04-24 12:23 ` Jiri Olsa
2021-04-25 18:03 ` Namhyung Kim
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=YIa3vXJrVwN44mjx@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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 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).