qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <alex@csgraf.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] OSX x86_32 host support
Date: Tue, 15 Jan 2008 17:32:01 +0100	[thread overview]
Message-ID: <478CE001.4000907@csgraf.de> (raw)
In-Reply-To: <20080115131359.GC11941@shareable.org>

Jamie Lokier wrote:
> Alexander Graf wrote:
>   
>> I believe the 5% performance hit  
>> that goes with them is no real problem, as most people should be using  
>> x86_64 nowadays anyway.
>>     
>
> *Boggle*!  x86_64 is only a few years old, and cheap low-power x86_64
> laptops are relatively recent.
>
> -- Jamie
>
>   
So you really want to do dynamic retranslation on ancient hardware? To
me emulated systems already feel slow on really recent machines, I
don't  want to go back to something even slower.
If you use kqemu there even is near no performance hit at all, which I
believe is the main use of qemu on i386 anyway. Furthermore x86_64 is
_way_ faster, as it provides a lot more registers.

I think the benefit you get from cutting the gcc3 dependency is way more
important than a major performance hit that people will usually only see
on the next release of qemu, by which time things have shifted towards
x86_64 even more.

Regards,

Alex

  reply	other threads:[~2008-01-15 16:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 23:43 [Qemu-devel] [PATCH] OSX x86_32 host support Mike Kronenberg
2008-01-14  8:25 ` Alexander Graf
2008-01-14  8:48   ` Mike Kronenberg
2008-01-15 13:14   ` Jamie Lokier
2008-01-15 16:32     ` Alexander Graf [this message]
2008-01-15 16:52       ` Jamie Lokier
2008-01-15 16:56       ` Johannes Schindelin
2008-01-15 17:30       ` Andreas Färber
2008-01-15 17:50         ` Alexander Graf
2008-01-15 18:11           ` Alexander Graf
2008-01-15 18:23           ` Thiemo Seufer
2008-01-15 18:51             ` Alexander Graf
2008-01-15 19:10           ` Andreas Färber

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=478CE001.4000907@csgraf.de \
    --to=alex@csgraf.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).