From: Jiri Olsa <jolsa@redhat.com>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: acme@kernel.org, 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 v4] perf stat: Show percore counts in per CPU output
Date: Sun, 16 Feb 2020 23:54:07 +0100 [thread overview]
Message-ID: <20200216225407.GB157041@krava> (raw)
In-Reply-To: <20200214080452.26402-1-yao.jin@linux.intel.com>
On Fri, Feb 14, 2020 at 04:04:52PM +0800, Jin Yao wrote:
SNIP
> CPU1 1,009,312 cpu/event=cpu-cycles,percore/
> CPU2 2,784,072 cpu/event=cpu-cycles,percore/
> CPU3 2,427,922 cpu/event=cpu-cycles,percore/
> CPU4 2,752,148 cpu/event=cpu-cycles,percore/
> CPU6 2,784,072 cpu/event=cpu-cycles,percore/
> CPU7 2,427,922 cpu/event=cpu-cycles,percore/
>
> 1.001416041 seconds time elapsed
>
> v4:
> ---
> Ravi Bangoria reports an issue in v3. Once we offline a CPU,
> the output is not correct. The issue is we should use the cpu
> idx in print_percore_thread rather than using the cpu value.
Acked-by: Jiri Olsa <jolsa@kernel.org>
btw, there's slight misalignment in -I output, but not due
to your change, it's there for some time now, and probably
in other agregation outputs as well:
$ sudo ./perf stat -e cpu/event=cpu-cycles/ -a -A -I 1000
# time CPU counts unit events
1.000224464 CPU0 7,251,151 cpu/event=cpu-cycles/
1.000224464 CPU1 21,614,946 cpu/event=cpu-cycles/
1.000224464 CPU2 30,812,097 cpu/event=cpu-cycles/
should be (extra space after CPUX):
1.000224464 CPU2 30,812,097 cpu/event=cpu-cycles/
I'll put it on my TODO, but if you're welcome to check on it ;-)
thanks,
jirka
next prev parent reply other threads:[~2020-02-16 22:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 8:04 [PATCH v4] perf stat: Show percore counts in per CPU output Jin Yao
2020-02-16 22:54 ` Jiri Olsa [this message]
2020-02-17 1:22 ` Jin, Yao
2020-02-17 11:06 ` Jiri Olsa
2020-02-18 1:02 ` Jin, Yao
2020-02-18 6:14 ` Jiri Olsa
2020-02-17 14:45 ` Arnaldo Carvalho de Melo
2020-03-19 14:10 ` [tip: perf/core] " tip-bot2 for 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=20200216225407.GB157041@krava \
--to=jolsa@redhat.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--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 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.