From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: Q: sched_clock() vs. clocksource, how to implement correctly
Date: Sun, 25 Apr 2010 16:36:14 +0200 [thread overview]
Message-ID: <1272206174.5289.1.camel@twins> (raw)
In-Reply-To: <20100424205011.GA21632@sig21.net>
On Sat, 2010-04-24 at 22:50 +0200, Johannes Stezenbach wrote:
> Somehow I got the impression that cnt32_to_63() is old-style,
Not really, the biggest problem it has is that is not SMP aware. I did
some patches for that at one time, but people objected for some reason.
next prev parent reply other threads:[~2010-04-25 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 15:09 Q: sched_clock() vs. clocksource, how to implement correctly Johannes Stezenbach
2010-04-23 16:29 ` Martin Schwidefsky
2010-04-24 20:50 ` Johannes Stezenbach
2010-04-25 14:36 ` Peter Zijlstra [this message]
2010-04-26 13:18 ` Johannes Stezenbach
2010-04-26 23:48 ` Daniel Walker
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=1272206174.5289.1.camel@twins \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).