qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.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 19:29:13 +0000	[thread overview]
Message-ID: <CAAu8pHskyatC8ZXWFfyjOodq=+KdGapJrvLFnSDpfQaWYL+yRg@mail.gmail.com> (raw)
In-Reply-To: <5052DF3A.1070007@msgid.tls.msk.ru>

On Fri, Sep 14, 2012 at 7:39 AM, Michael Tokarev <mjt@tls.msk.ru> 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?

i386 should not allow executing x86_64 code or using other 64 bit
features but raise exceptions. 64 bit CPU models should not be
available to i386 emulator. Physical memory is limited to PAE maximum
for i386.

We could also let x86_64 diverge from i386 and remove legacy devices
to emulate a modern legacy free system while keeping i386 closer to
1990s machines, though this would be mainly a linkage issue.

>
> Thanks,
>
> /mjt
>

      parent reply	other threads:[~2012-09-14 19:43 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
2012-09-14 19:29 ` Blue Swirl [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='CAAu8pHskyatC8ZXWFfyjOodq=+KdGapJrvLFnSDpfQaWYL+yRg@mail.gmail.com' \
    --to=blauwirbel@gmail.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 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).