Messages in this thread | | | Subject | Re: Athlon64x2 problem with 2.6.18-rt4 and hrtimers | From | Lee Revell <> | Date | Wed, 27 Sep 2006 18:50:59 -0400 |
| |
On Wed, 2006-09-27 at 23:59 +0200, Thomas Gleixner wrote: > Can you please switch on CONFIG_LATENCY_TRACE (depends on > CONFIG_LATENCY_TIMING) ? > > Use the latest version of cyclictest and add -b XXX to the command > line, > where XXX is the maximum latency in micro seconds. Once the latency is > greater than the given maximum, the kernel tracer and cyclictest is > stopped. > > Now you can read the kernel trace: > > cat /proc/latency_trace >trace.log > > The trace should give us more insight.
I thought latency tracing did not work on Athlon X2 due to the unsynced TSCs problem?
Lee
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |