13 Oct
2011
13 Oct
'11
4:20 a.m.
On 10/13/2011 01:28 AM, Michael Ost wrote:
At the output? - why not. just post it. At the problem? mmh maybe,
sounds like a lot of initial setup work.
On 10/07/2011
08:07 PM, Robin Gareus wrote:
It's a bit dated but so is your 2.6.24.3 kernel. You will need to
compile the kernel with CONFIG_PREEMPT_TRACER=y CONFIG_SCHED_TRACER=y
under "Kernel hacking -> Tracers -> .." to get access to
/sys/kernel/debug/tracing/
I've got some output, but am not having much luck parsing it or figuring
it out. Would you (or anyone else on the list) be willing to take a look
at it? I'm using a 2.6.33.7 kernel, by the way.
Cheers... mo
mount -t debugfs debugfs /sys/kernel/debug
echo wakeup_rt > /sys/kernel/debug/tracing/current_tracer
cyclictest -m -p 80 -b 200 -f -T wakeup_rt
# cyclic-test shows Thread ID -> ps -> WHO is causing the delay?
cat /sys/kernel/debug/tracing/trace
# sheds light onto the WHY
HTH,
robin