qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] x86-64 port
Date: Wed, 17 Mar 2004 23:17:06 +0100	[thread overview]
Message-ID: <D355B5CB-7860-11D8-AEC0-003065C7D858@mandrakesoft.com> (raw)
In-Reply-To: <4058BFD6.1030200@bellard.org>

Hi,

> Nick Snellock wrote:
>> Is anyone working on an x86-64 port?
>
> Not me :-) An x86-64 host port would be very interesting because the 
> 64 bit host MMU could be used to remap the whole emulated 4GB address 
> space.

Fabrice, remember that I posted AMD64 support bits to the list some 
time ago? ;-) This works for user mode applications. As for the soft 
mmu, the current code is not 64-bit clean. I had some patches but they 
were not enough and are in a dormant state since. So remapping the 
whole 4GB address space is probably a faster and simpler fix indeed.

> I think that there is also a lot of potential for a "code-copy" mode 
> converting x86-32 to x86-64 code (look at what I did for . Along with 
> the 4GB space remapping, it would give close to native performances 
> without requiring any potentially unsafe kernel module (unlike the 
> popular virtualizers).

The popular virtualizers don't officially support AMD64 host systems 
yet. Vmware 4.5 is expected to do so though.

  reply	other threads:[~2004-03-17 22:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 18:32 [Qemu-devel] x86-64 port Nick Snellock
2004-03-17 21:15 ` Fabrice Bellard
2004-03-17 22:17   ` Gwenole Beauchesne [this message]
2004-03-17 23:06     ` Fabrice Bellard
2004-03-17 23:15       ` Fabrice Bellard
2004-03-17 23:51     ` Fabrice Bellard
2004-03-18  1:40   ` [Qemu-devel] " Andi Kleen

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=D355B5CB-7860-11D8-AEC0-003065C7D858@mandrakesoft.com \
    --to=gbeauchesne@mandrakesoft.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 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).