Hi Peter,
On Mon, 11 Mar 2013 11:01:14 +0100, Peter Zijlstra wrote:
> On Thu, 2013-03-07 at 13:19 +0900, Namhyung Kim wrote:
>> From: Namhyung Kim
>>
>> There's a problem with mixed hw/sw group when the leader is a software
>> event. For instance:
>
>> Jiri's patch 0231bb533675 ("perf: Fix
On Thu, 2013-03-07 at 13:19 +0900, Namhyung Kim wrote:
> From: Namhyung Kim
>
> There's a problem with mixed hw/sw group when the leader is a software
> event. For instance:
> Jiri's patch 0231bb533675 ("perf: Fix event group context move") fixed
> a part of problem but there's a devil still..
On Thu, 2013-03-07 at 13:19 +0900, Namhyung Kim wrote:
From: Namhyung Kim namhyung@lge.com
There's a problem with mixed hw/sw group when the leader is a software
event. For instance:
Jiri's patch 0231bb533675 (perf: Fix event group context move) fixed
a part of problem but there's a
Hi Peter,
On Mon, 11 Mar 2013 11:01:14 +0100, Peter Zijlstra wrote:
On Thu, 2013-03-07 at 13:19 +0900, Namhyung Kim wrote:
From: Namhyung Kim namhyung@lge.com
There's a problem with mixed hw/sw group when the leader is a software
event. For instance:
Jiri's patch 0231bb533675 (perf:
From: Namhyung Kim
There's a problem with mixed hw/sw group when the leader is a software
event. For instance:
$ perf stat -e '{task-clock,cycles,faults}' sleep 1
Performance counter stats for 'sleep 1':
0.273436 task-clock#0.000 CPUs utilized
From: Namhyung Kim namhyung@lge.com
There's a problem with mixed hw/sw group when the leader is a software
event. For instance:
$ perf stat -e '{task-clock,cycles,faults}' sleep 1
Performance counter stats for 'sleep 1':
0.273436 task-clock#0.000 CPUs
6 matches
Mail list logo