Do you want to know where your code waits locks for a long time?
Yes! It's for you. This feature helps you to find bottlenecks.
It's not artificial task. Once one of my colleague was investigating a
scalability problem. He pressed sysrq-t some times and tried to merge
call-chains by hand. But perf
Hello Arnaldo,
I found, that you commit patches for perf. Could you review this part?
Arun Sharma said, that the second versions of patches works ok for him.
(Arun is the first user of this functionality after me.)
Thanks.
On 11/28/2011 01:03 PM, Andrew Vagin wrote:
Do you want to know where
* Andrey Vagin wrote:
> Hello Arnaldo,
>
> I found, that you commit patches for perf. Could you review this part?
To help out this effort i have applied your new
kernel/sched/fair.c event to patch the scheduler
tree (tip:sched/core).
Note, i have renamed it from sched_stat_block to
sched_st
Em Tue, Dec 06, 2011 at 11:15:07AM +0400, Andrey Vagin escreveu:
> Hello Arnaldo,
>
> I found, that you commit patches for perf. Could you review this part?
>
> Arun Sharma said, that the second versions of patches works ok for him.
> (Arun is the first user of this functionality after me.)
I'm
On 12/5/11 11:15 PM, Andrey Vagin wrote:
Arun Sharma said, that the second versions of patches works ok for him.
(Arun is the first user of this functionality after me.)
Yes - Andrey's patches (v2) have been functional for me when used via:
perf record -agP -e sched:sched_switch --filter "pre
