From: Andi Kleen <ak@muc.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: x86-64 port
Date: Thu, 18 Mar 2004 02:40:16 +0100 [thread overview]
Message-ID: <m3smg7exvj.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <4058BFD6.1030200@bellard.org> (Fabrice Bellard's message of "Wed, 17 Mar 2004 22:15:02 +0100")
Fabrice Bellard <fabrice@bellard.org> writes:
> 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.
I tried to run it recently in 32bit emulation on the 64bit kernel,
but it just produced a lot of segfaults. Even when I forced the
address room to 3GB. Most likely it triggers bugs in the 32bit emulation
layer. I wasn't able to look into it yet.
> 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).
Yes, and you may even get better code in the result (you have 16 registers
to play with instead of 8)
There is one problem however: currently there are a few system calls
that know if they are executing in 32bit or 64bit and act accordingly.
You can call the 32bit int 0x80 system call handler from a 64bit process,
but you would probably run into smaller issues. This may need a few kernel
fixes. For example the environment and some other pointers are 64bit.
Should be all fixable though.
-Andi
prev parent reply other threads:[~2004-03-18 1:41 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
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 ` Andi Kleen [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=m3smg7exvj.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--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.