From: Wink Saville <wink@saville.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] x86: unify/rewrite SMP TSC sync code
Date: Mon, 27 Nov 2006 01:15:53 -0800 [thread overview]
Message-ID: <456AACC9.10206@saville.com> (raw)
In-Reply-To: <1164613914.3276.10.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> just to make sure, you do realize that when you write "ticks" that rdtsc
> doesn't measure cpu clock ticks or cpu cycles anymore, right? (At least
> not on your machine)
>
Yes, that's why I wrote ticks and not cycles. At this point I'm not sure how to convert
ticks to time on my machine, something else to learn:) Hopefully the HPET
will resolve all of the issues.
Wink
next prev parent reply other threads:[~2006-11-27 9:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa./NRPJg+JjfSQLUVwnX1GpHGIojQ@ifi.uio.no>
[not found] ` <fa.Y0RKABHd+7qnbGQYBAGPvlJ0Qic@ifi.uio.no>
[not found] ` <fa.fD3WSpNqEJ4736vYzEak5Gf3xTw@ifi.uio.no>
[not found] ` <fa.A+gkQAO1DLThaxJxPLPl3yE1CGo@ifi.uio.no>
[not found] ` <fa.INurNKWdUKAEULTHyfpSW65a/Ng@ifi.uio.no>
[not found] ` <fa.n9vySiI9RS2MCl0DZPDzxZEPiFw@ifi.uio.no>
2006-11-26 7:20 ` [patch] x86: unify/rewrite SMP TSC sync code Robert Hancock
2006-11-26 8:16 ` Wink Saville
2006-11-26 8:24 ` Arjan van de Ven
2006-11-26 19:48 ` Wink Saville
2006-11-27 7:51 ` Arjan van de Ven
2006-11-27 9:15 ` Wink Saville [this message]
2006-11-27 17:23 Robert Crocombe
2006-11-27 18:41 ` Max Krasnyansky
-- strict thread matches above, loose matches on Subject: below --
2006-11-24 17:02 Ingo Molnar
2006-11-24 17:13 ` Andi Kleen
2006-11-24 20:25 ` Ingo Molnar
2006-11-24 20:37 ` Andi Kleen
2006-11-24 20:46 ` Ingo Molnar
2006-11-24 21:06 ` Andi Kleen
2006-11-24 22:48 ` Ben Greear
2006-11-25 2:56 ` Wink Saville
2006-11-25 8:30 ` Arjan van de Ven
2006-11-25 16:58 ` Wink Saville
2006-11-25 17:41 ` Arjan van de Ven
2006-11-25 20:34 ` Wink Saville
2006-11-27 19:00 ` Christoph Lameter
2006-11-29 7:13 ` 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=456AACC9.10206@saville.com \
--to=wink@saville.com \
--cc=arjan@infradead.org \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
/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