All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
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 14:37:37 +0000	[thread overview]
Message-ID: <20090127143736.GA18646@shareable.org> (raw)
In-Reply-To: <497ED233.7010504@suse.de>

Alexander Graf wrote:
> 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.

TCG doesn't use the available x86_64 registers when generating code
for 32-bit operations on an x86_64 host?

> I would be very surprised if the improvement of emulating x86_64 on x86
> vs. x86_64 is only ~10%.

So would I.

By the way, with KVM, can QEMU (the I/O model) be a 32-bit app while
the KVM kernel module provides an x86_64 CPU?

That might be useful, if there are advantages to QEMU itself being
32-bit on MacOS X and if there's a KVM module for it.

-- Jamie

  reply	other threads:[~2009-01-27 14:37 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
2009-01-27 14:37             ` Jamie Lokier [this message]
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=20090127143736.GA18646@shareable.org \
    --to=jamie@shareable.org \
    --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.