From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "Jin, Yao" <yao.jin@linux.intel.com>,
jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2] perf stat: Append to default list if use -e +event
Date: Wed, 20 Jan 2021 21:03:55 -0300 [thread overview]
Message-ID: <20210121000355.GB106434@kernel.org> (raw)
In-Reply-To: <20210120212553.GA1798087@krava>
Em Wed, Jan 20, 2021 at 10:25:53PM +0100, Jiri Olsa escreveu:
> On Mon, Jan 18, 2021 at 12:54:37PM +0800, Jin, Yao wrote:
> > root@kbl-ppc:# ./perf stat -e +power/energy-pkg/ -a -- sleep 1
> > Performance counter stats for 'system wide':
> > 2.02 Joules +power/energy-pkg/
> > 1.000859434 seconds time elapsed
> > The '+' prefix is printed. So I finally decide not to remove the '+' prefix
> > in order to keep original behavior.
> hm, originaly there's no purpose for the '+', right?
> it seems it's more like bug then anything else
> you added function to the '+' to add default events to specified event,
> which I think is good idea, but I don't think we should display the
> extra '+' in output
The value would be to stress that that is an event added to the ones
without the + prefix, i.e. the default ones.
But by having the command line copied over and the added events at the
first lines we should have that abundantly clear.
Also we won't print removed events (using -), is that available already?
Nope:
[root@quaco ~]# perf stat -e -cycles sleep
event syntax error: '-cycles'
\___ parser error
Run 'perf list' for a list of valid events
Usage: perf stat [<options>] [<command>]
-e, --event <event> event selector. use 'perf list' to list available events
[root@quaco ~]#
Like with:
[root@quaco ~]# perf stat -d sleep 1
Performance counter stats for 'sleep 1':
0.80 msec task-clock # 0.001 CPUs utilized
1 context-switches # 0.001 M/sec
0 cpu-migrations # 0.000 K/sec
59 page-faults # 0.073 M/sec
2,215,522 cycles # 2.757 GHz (7.40%)
1,073,189 instructions # 0.48 insn per cycle (80.59%)
203,615 branches # 253.392 M/sec
8,309 branch-misses # 4.08% of all branches
245,866 L1-dcache-loads # 305.972 M/sec
14,024 L1-dcache-load-misses # 5.70% of all L1-dcache accesses (92.60%)
<not counted> LLC-loads (0.00%)
<not counted> LLC-load-misses (0.00%)
1.001887261 seconds time elapsed
0.000000000 seconds user
0.001413000 seconds sys
Some events weren't counted. Try disabling the NMI watchdog:
echo 0 > /proc/sys/kernel/nmi_watchdog
perf stat ...
echo 1 > /proc/sys/kernel/nmi_watchdog
[root@quaco ~]# perf stat -e -LLC* -d sleep 1
event syntax error: '-LLC*'
\___ parser error
Run 'perf list' for a list of valid events
Usage: perf stat [<options>] [<command>]
-e, --event <event> event selector. use 'perf list' to list available events
[root@quaco ~]#
- Arnaldo
next prev parent reply other threads:[~2021-01-21 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 2:18 [PATCH v2] perf stat: Append to default list if use -e +event Jin Yao
2021-01-12 10:08 ` Jiri Olsa
2021-01-18 4:54 ` Jin, Yao
2021-01-20 21:25 ` Jiri Olsa
2021-01-21 0:03 ` Arnaldo Carvalho de Melo [this message]
2021-01-21 6:08 ` Jin, Yao
2021-01-21 13:02 ` Arnaldo Carvalho de Melo
2021-01-22 1:43 ` Jin, Yao
2021-01-23 23:14 ` Jiri Olsa
2021-01-21 5:05 ` Jin, Yao
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=20210121000355.GB106434@kernel.org \
--to=acme@kernel.org \
--cc=Linux-kernel@vger.kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.intel.com \
/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