From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] Enabled building of x86_64 code on Mac OS X
Date: Tue, 27 Jan 2009 10:21:55 +0100 [thread overview]
Message-ID: <497ED233.7010504@suse.de> (raw)
In-Reply-To: <497E61DE.2080802@us.ibm.com>
Anthony Liguori wrote:
> Paul Brook wrote:
>> I did say overall performance.
>> My experience with AMD hardware is that you generally get ~10%
>> overall improvement from LP64. Intel hardware (particularly the early
>> 64-bit cores) less so, but it's generally still a win.
>>
>> I guess ILP32 long mode would probably increase that further, and
>> avoid the odd regressions. It's an awful lot of work to implement
>> though, especially on a target that isn't used to having lots of
>> incompatible variants.
>>
>
> I expected a performance boost. Since OS X only runs on Intel CPUs, I
> don't think it's dramatically worth it to get a few percent CPU
> improvement. The reason I asked is that if we decided to drop Cocoa
> in favor of SDL, it would prevent the use of 64-bit.
The extra registers should speed up things quite a bit. While that's not
too much of a problem when emulating x86, which has few registers
anyway, emulating a ppc or x86_64 target should be faster on an x86_64
host. I haven't done measurements though.
As for the plus in code size on x86_64 - that doesn't really apply to
tcg, as that still generates 32-bit code when only 32-bit code is
necessary, which still looks the same on x86_64. Plus it does simplify
64-bit operations.
I would be very surprised if the improvement of emulating x86_64 on x86
vs. x86_64 is only ~10%.
Alex
next prev parent reply other threads:[~2009-01-27 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 19:44 [Qemu-devel] [PATCH] Enabled building of x86_64 code on Mac OS X Alexander Graf
2009-01-26 15:40 ` Anthony Liguori
2009-01-27 0:34 ` Paul Brook
2009-01-27 0:42 ` Jamie Lokier
2009-01-27 0:59 ` Paul Brook
2009-01-27 1:22 ` Anthony Liguori
2009-01-27 9:21 ` Alexander Graf [this message]
2009-01-27 14:37 ` Jamie Lokier
2009-01-27 15:00 ` Laurent Desnogues
2009-01-27 0:40 ` C.W. Betts
2009-01-27 0:40 ` C.W. Betts
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=497ED233.7010504@suse.de \
--to=agraf@suse.de \
--cc=paul@codesourcery.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 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.