From: Lee Revell <rlrevell@joe-job.com>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: sched_clock -> check_tsc_unstable -> tsc_read_c3_time ?!?
Date: Thu, 13 Oct 2005 16:13:26 -0400 [thread overview]
Message-ID: <1129234407.16243.58.camel@mindpipe> (raw)
In-Reply-To: <1129234306.27168.7.camel@cog.beaverton.ibm.com>
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?
Lee
next prev parent reply other threads:[~2005-10-13 20:13 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 [this message]
2005-10-14 4:35 ` Ingo Molnar
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=1129234407.16243.58.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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