On 3/16/2019 7:26 AM, Andi Kleen wrote:
Yes, the coresum's behavior is similar as --per-core option, just supports
at the event level. I'm OK with calling it 'per-core'.
For example,
perf stat -e cpu/event=0,umask=0x3,per-core=1/
Please use percore, the - would need to be escaped in metric
> Yes, the coresum's behavior is similar as --per-core option, just supports
> at the event level. I'm OK with calling it 'per-core'.
>
> For example,
> perf stat -e cpu/event=0,umask=0x3,per-core=1/
Please use percore, the - would need to be escaped in metric expressions.
-Andi
On 3/15/2019 9:34 PM, Jiri Olsa wrote:
On Sat, Mar 16, 2019 at 12:04:13AM +0800, Jin Yao wrote:
The coresum event qualifier which sums up the event counts for both
hardware threads in a core. For example,
perf stat -e cpu/event=0,umask=0x3,coresum=1/,cpu/event=0,umask=0x3/
In this example,
On Sat, Mar 16, 2019 at 12:04:13AM +0800, Jin Yao wrote:
> The coresum event qualifier which sums up the event counts for both
> hardware threads in a core. For example,
>
> perf stat -e cpu/event=0,umask=0x3,coresum=1/,cpu/event=0,umask=0x3/
>
> In this example, we count the event 'ref-cycles' p
The coresum event qualifier which sums up the event counts for both
hardware threads in a core. For example,
perf stat -e cpu/event=0,umask=0x3,coresum=1/,cpu/event=0,umask=0x3/
In this example, we count the event 'ref-cycles' per-core and per-CPU in
one perf stat command-line.
We can already su
5 matches
Mail list logo
