* Jörn Engel <[email protected]> wrote:
> > oprofile helps if you can reliably reproduce the slowdown in a loop
> > or for a long amount of time, with lots of CPU utilization - and
> > then it's also lower overhead. The tracer can be used to capture
> > rare or complex events, and gives the full flow control and what is
> > happening within the kernel.
>
> Such a trace would be useful indeed. But so far the patch has only
> given me grief and nothing remotely like useful output. Maybe I
> should simply use the complete -rt patch instead of debugging the
> broken-out latency-tracer patch.
to capture that trace i did not use -rt, i just patched latest -git
with:
http://people.redhat.com/mingo/latency-tracing-patches/latency-tracing-v2.6.24-rc3.combo.patch
(this has your fixes included already)
have done:
echo 1 > /proc/sys/kernel/mcount_enabled
and have run:
./trace-cmd sleep 1 > trace.txt
http://people.redhat.com/mingo/latency-tracing-patches/trace-cmd.c
to capture a 1 second trace of what the system is doing. I think your
troubles are due to running it within a qemu guest - that is not a
typical utilization so you are on unchartered waters.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
