All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-system-i386 vs qemu-system-x86_64 ?
Date: Fri, 14 Sep 2012 12:00:39 +0200	[thread overview]
Message-ID: <50530047.9030703@siemens.com> (raw)
In-Reply-To: <5052FB60.3060109@msgid.tls.msk.ru>

On 2012-09-14 11:39, Michael Tokarev wrote:
> On 14.09.2012 13:33, Daniel P. Berrange wrote:
>> On Fri, Sep 14, 2012 at 11:39:38AM +0400, Michael Tokarev wrote:
>>> What's the difference between the two except that the
>>> latter adds some more instructions (actually whole new
>>> subsytem) to the former?  Why do we need -i386, what
>>> -x86_64 does not do which does -i386?
>>
>> AFAIK,  qemu-system-x86_64 does not support KVM on a 32-bit host.
> 
> Isn't it the other way around?
> 
> Or, does qemu-system-i386 EVER support kvm?

It does support KVM on 32-bit (minus undiscovered bugs in 32-bit-only
kernel code paths once in a while - none known right now, though). Don't
confuse old qemu-kvm with QEMU here. The latter always supported KVM
with both variants, and qemu-kvm now also does as it stopped being
different.

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).

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-09-14 10:00 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 [this message]
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
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=50530047.9030703@siemens.com \
    --to=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.