From: Ingo Molnar <mingo@elte.hu>
To: Lee Revell <rlrevell@joe-job.com>
Cc: john stultz <johnstul@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: sched_clock -> check_tsc_unstable -> tsc_read_c3_time ?!?
Date: Fri, 14 Oct 2005 06:35:55 +0200 [thread overview]
Message-ID: <20051014043555.GA13595@elte.hu> (raw)
In-Reply-To: <1129234407.16243.58.camel@mindpipe>
* Lee Revell <rlrevell@joe-job.com> wrote:
> On Thu, 2005-10-13 at 13:11 -0700, john stultz wrote:
> > Yea, you're right about the inlining. Although I'm not sure why those
> > functions should take microseconds to execute. That's very strange.
>
> Latency tracing overhead plus a slow (600MHz) machine?
yeah. The micro-timings of latency tracing can be misleading. Function
calls are very fast on most CPUs (even on a 600MHz one), but with the
latency tracer generating one trace entry per function call, there's
considerable added overhead.
we could in theory calibrate the tracing overhead and subtract it from
cycle readings [i've done this in a previous mcount() based tracer
implementation, years ago], but that would make the latency trace
timestamps less useful as a global time reference.
Ingo
prev parent reply other threads:[~2005-10-14 4:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 20:01 sched_clock -> check_tsc_unstable -> tsc_read_c3_time ?!? Lee Revell
2005-10-13 20:11 ` john stultz
2005-10-13 20:13 ` Lee Revell
2005-10-14 4:35 ` Ingo Molnar [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=20051014043555.GA13595@elte.hu \
--to=mingo@elte.hu \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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