From: Aurelien Jarno <aurelien@aurel32.net>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-system-i386 vs qemu-system-x86_64 ?
Date: Fri, 14 Sep 2012 14:24:57 +0200 [thread overview]
Message-ID: <20120914122457.GA7373@ohm.aurel32.net> (raw)
In-Reply-To: <5053010E.1000103@msgid.tls.msk.ru>
On Fri, Sep 14, 2012 at 02:03:58PM +0400, Michael Tokarev wrote:
> On 14.09.2012 14:00, Jan Kiszka wrote:
> []
> > The major difference in qemu-system-i386 vs. qemu-system-x86_64 is on
> > the TCG side: We measured noticeable performance benefits when running
> > 32/16 bit OSes against qemu-system-i386 vs. using qemu-system-x86_64. I
> > don't have numbers at hand, but colleagues decided to use the 32-bit
> > version for that reason (when no KVM is available).
>
> Interesting. Maybe someone should look at the difference on TCG side
> and merge interesting bits from i386 to x86_64... :)
Most of the code between i386 and x86_64 is basically the same. For
improving TCG performances, the only interesting thing to merge from i386 to
x86_64 would be the use 32-bit registers instead of 64-bit registers. Oh
wait...
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2012-09-14 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 7:39 [Qemu-devel] qemu-system-i386 vs qemu-system-x86_64 ? Michael Tokarev
2012-09-14 9:33 ` Daniel P. Berrange
2012-09-14 9:39 ` Michael Tokarev
2012-09-14 10:00 ` Jan Kiszka
2012-09-14 10:03 ` Michael Tokarev
2012-09-14 10:12 ` Jan Kiszka
2012-09-14 10:20 ` Daniel P. Berrange
2012-09-14 10:32 ` Jan Kiszka
2012-09-14 10:39 ` Peter Maydell
2012-09-14 12:24 ` Aurelien Jarno [this message]
2012-09-14 19:29 ` Blue Swirl
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=20120914122457.GA7373@ohm.aurel32.net \
--to=aurelien@aurel32.net \
--cc=jan.kiszka@siemens.com \
--cc=mjt@tls.msk.ru \
--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.