From: Lee Revell <rlrevell@joe-job.com>
To: tglx@linutronix.de
Cc: Clark Williams <williams@redhat.com>, Ingo Molnar <mingo@elte.hu>,
john stultz <johnstul@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Athlon64x2 problem with 2.6.18-rt4 and hrtimers
Date: Wed, 27 Sep 2006 18:50:59 -0400 [thread overview]
Message-ID: <1159397459.1275.55.camel@mindpipe> (raw)
In-Reply-To: <1159394364.9326.560.camel@localhost.localdomain>
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
prev parent reply other threads:[~2006-09-27 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 20:30 Athlon64x2 problem with 2.6.18-rt4 and hrtimers Clark Williams
2006-09-27 21:59 ` Thomas Gleixner
2006-09-27 22:32 ` Clark Williams
2006-09-27 22:50 ` Lee Revell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1159397459.1275.55.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox