From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/hw mips_r4k.c
Date: Wed, 3 May 2006 00:29:24 +0100 [thread overview]
Message-ID: <20060502232924.GJ5004@networkno.de> (raw)
In-Reply-To: <E1Fb3CO-0000VX-4T@savannah.gnu.org>
Fabrice Bellard wrote:
> CVSROOT: /sources/qemu
> Module name: qemu
> Branch:
> Changes by: Fabrice Bellard <bellard@savannah.gnu.org> 06/05/02 22:18:28
>
> Modified files:
> hw : mips_r4k.c
>
> Log message:
> performance boost (on P4 hosts at least, rdtsc is a _very_ bad random generator)
>
> CVSWeb URLs:
> http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/hw/mips_r4k.c.diff?tr1=1.15&tr2=1.16&r1=text&r2=text
Does this really provide a measurable performance improvement?
Real hardware simply increments cp0_random together with the cycle
counter, this is randomized enough for TLB entry replacement.
Thiemo
next prev parent reply other threads:[~2006-05-02 23:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 22:18 [Qemu-devel] qemu/hw mips_r4k.c Fabrice Bellard
2006-05-02 23:29 ` Thiemo Seufer [this message]
2006-05-03 19:11 ` Fabrice Bellard
2006-05-03 19:46 ` Thiemo Seufer
-- strict thread matches above, loose matches on Subject: below --
2007-12-07 1:13 Thiemo Seufer
2007-11-11 12:02 Paul Brook
2007-10-13 14:00 Thiemo Seufer
2007-03-17 15:21 Thiemo Seufer
2007-01-06 2:24 Thiemo Seufer
2007-01-06 1:37 Thiemo Seufer
2007-01-01 20:31 Thiemo Seufer
2006-12-23 0:23 Thiemo Seufer
2006-05-11 21:15 Fabrice Bellard
2006-05-11 21:46 ` Thiemo Seufer
2006-05-11 22:50 ` Fabrice Bellard
2006-04-26 22:06 Fabrice Bellard
2005-12-18 17:51 Fabrice Bellard
2005-12-05 19:56 Fabrice Bellard
2005-08-21 9:40 Fabrice Bellard
2005-07-02 18:11 Fabrice Bellard
2005-07-02 15:20 Fabrice Bellard
2005-07-02 15:13 Fabrice Bellard
2005-07-02 15:11 Fabrice Bellard
2005-07-02 14:58 Fabrice Bellard
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=20060502232924.GJ5004@networkno.de \
--to=ths@networkno.de \
--cc=qemu-devel@nongnu.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).