public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Clark Williams <williams@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.15-rt4 failure with LATENCY_TRACE on x86_64
Date: Fri, 13 Jan 2006 10:54:39 -0500	[thread overview]
Message-ID: <1137167679.7241.25.camel@localhost.localdomain> (raw)
In-Reply-To: <1137164761.3332.2.camel@localhost.localdomain>

On Fri, 2006-01-13 at 09:06 -0600, Clark Williams wrote:
> On Thu, 2006-01-12 at 22:18 -0500, Steven Rostedt wrote:
> > OK, I'm actually sending you this email on a x86_64 running
> > 2.6.15-rt4-sr2, with latency tracing on.  But unfortunately, I have a
> > AMD X2 that each core has it's own tsc counter that is not in sync, and
> > since the latency tracer uses tsc, I get garbage.  But beware, the tsc
> > does slow down when the cpu idles, so it gives bad results even for non
> > x2 systems.
> > 
> Hmm, I didn't realize that (I'm running on a uni-processor system). I
> just pulled your rt4-sr2 patch and will apply/rebuild/test. 
> 
> > I finally was able to boot this with using the PM timer, but the
> > beginning of my dmesg is still filled with:
> > 
> > read_tsc: ACK! TSC went backward! Unsynced TSCs?
> > 
> > Have you tried booting with idle=poll? I wonder if that would help?
> 
> No, I thought that was strictly an SMP issue. I'll try it as well.

It effects SMP mostly.  I doubt that it will effect UP, but the tsc is
still not consistent.

-- Steve



  reply	other threads:[~2006-01-13 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1137103652.11354.40.camel@localhost.localdomain>
2006-01-13  3:18 ` 2.6.15-rt4 failure with LATENCY_TRACE on x86_64 Steven Rostedt
2006-01-13 15:06   ` Clark Williams
2006-01-13 15:54     ` Steven Rostedt [this message]
2006-01-13 22:58       ` Clark Williams
2006-01-13 23:08         ` Steven Rostedt
2006-01-14  5:12           ` Mikael Andersson
2006-01-15 18:59             ` Clark Williams

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=1137167679.7241.25.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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