On 11/2/11 3:59 PM, Andrew Vagin wrote:I didn't see any warning, but I reworked this part a bit.
+ event_sw = (union perf_event *)&ent->header;
This causes problems with -Wstrict-aliasing=3.
I noticed that the suggested cmdline is:
perf script record sched-stat -- -e sched:sched_stat_sleep
I'd much prefer something along the lines of:
perf script record sched-stat -e <events> -- sleep 1
Also, the perf inject command is a bit unforgiving when the user makes
some mistakes (eg: didn't specify -e sched:sched_stat_sleep). The
failure mode is hard to understand (perf report -i perf.data.d fails
with "no samples").
Could not find sched_switch for pid 16179Actually It isn't. Now I print this message as debug information.
I think this is the same issue you referenced in "Known issues".
It's strange. Can you check new versions and describe the experiment if it will be reproduces.
Although I'm able to get some profiling info out of perf.data.d, the
process I really wanted to trace got zero samples.
-Arun