From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: sparc64 lazy conditional codes evaluation
Date: Sat, 15 May 2010 13:56:15 +0100 [thread overview]
Message-ID: <4BEE99EF.1020202@siriusit.co.uk> (raw)
In-Reply-To: <k2lf43fc5581005101133wd185ae8cn5c8990ec882e376f@mail.gmail.com>
Blue Swirl wrote:
> Guest time can be unreliable, it could also indicate that Linux
> executes a lot more timer interrupts. Could you retest and measure the
> wall clock time?
>
> I think the C flag change should only increase performance. The next
> commit may have negative effects because more work is done every
> interrupt, but it's also more correct now.
Hmmm looks like you're right. I did a few more tests measuring wall
clock time and averaging across a set of runs gives roughly the same
time (although there does seem to be quite a bit of variation in
resulting times on my system here). So nothing to worry about here.
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs
prev parent reply other threads:[~2010-05-15 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 7:17 [Qemu-devel] sparc64 lazy conditional codes evaluation Igor Kovalenko
2010-05-03 19:24 ` [Qemu-devel] " Blue Swirl
2010-05-03 19:46 ` Igor Kovalenko
2010-05-03 19:54 ` Blue Swirl
2010-05-03 20:03 ` Igor Kovalenko
2010-05-04 20:21 ` Blue Swirl
2010-05-05 20:24 ` Igor Kovalenko
2010-05-06 18:51 ` Blue Swirl
2010-05-08 6:41 ` Igor Kovalenko
2010-05-09 20:22 ` Blue Swirl
2010-05-10 9:40 ` Mark Cave-Ayland
2010-05-10 18:33 ` Blue Swirl
2010-05-15 12:56 ` Mark Cave-Ayland [this message]
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=4BEE99EF.1020202@siriusit.co.uk \
--to=mark.cave-ayland@siriusit.co.uk \
--cc=blauwirbel@gmail.com \
--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).