From: William Lee Irwin III <wli@holomorphy.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Theodore Ts'o <tytso@mit.edu>, Andrew Morton <akpm@osdl.org>,
Anton Blanchard <anton@samba.org>,
arnd@arndb.de, richm@oldelvet.org.uk, linux-arch@vger.kernel.org
Subject: Re: Using get_cycles for add_timer_randomness
Date: Mon, 16 Aug 2004 09:49:47 -0700 [thread overview]
Message-ID: <20040816164947.GC11200@holomorphy.com> (raw)
In-Reply-To: <20040816164420.GA22312@linux-mips.org>
On Mon, Aug 16, 2004 at 09:22:28AM -0700, William Lee Irwin III wrote:
>> AFAICT most of those return 0 from get_cycles().
On Mon, Aug 16, 2004 at 06:44:20PM +0200, Ralf Baechle wrote:
> The cycle counter on MIPS processors [1] is only 32-bit. I've been
> pondering to construct a 64-bit value in get_cycles() which would seriously
> slow down the function compared to the current single instruction
> implementation; fortunately a quick survey of all get_cycles() users a
> while ago did look like non of them actually requires the full 64-bit.
What does it return when the 32-bit cycle counter is not present? (It was
not obvious to me; it looks like it returns whatever's in $9.)
-- wli
next prev parent reply other threads:[~2004-08-16 16:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 1:03 Using get_cycles for add_timer_randomness Arnd Bergmann
2004-08-10 16:24 ` Anton Blanchard
2004-08-14 18:36 ` Anton Blanchard
2004-08-15 22:48 ` Andrew Morton
2004-08-15 23:46 ` Richard Mortimer
2004-08-15 23:59 ` David S. Miller
2004-08-16 16:17 ` Theodore Ts'o
2004-08-16 16:22 ` William Lee Irwin III
2004-08-16 16:44 ` Ralf Baechle
2004-08-16 16:49 ` William Lee Irwin III [this message]
2004-08-19 18:26 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 18:53 Luck, Tony
2004-08-16 21:29 Luck, Tony
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=20040816164947.GC11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=richm@oldelvet.org.uk \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.