From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, jmfguy@excite.com
Subject: Re: [Qemu-devel] qemu for x86_64
Date: Thu, 30 Sep 2004 17:06:50 +0100 [thread overview]
Message-ID: <200409301706.50083.paul@codesourcery.com> (raw)
In-Reply-To: <20040930154044.880CF3D0A@xprdmailfe4.nwk.excite.com>
> x86_64 is only an extension, a super-set, of the existing 32 bit
> architecture. This is not some completely different instruction set. Qemu
> already has most of the work finished in the 32 bit x86 version. The GNU
> GCC developers claimed porting GCC to amd64 was "easy", so you can forget
> the car. This should be an easy port for one of the primary maintainers. If
> I knew the code well, I'd do it myself but, I'm still working on Qemu
> networking.
Porting to gcc to amd64 is only "easy" compared to porting to a whole new
architecture (eg. ia64).
Also, calling x86_64 "only an extension" isn't really accurate. This totally
ignores the fact that you need to make sure the qemu i386 backend is 64-bit
safe (I'm fairly sure it isn't), plus implement MMX and SSE.
Compare the cost of an amd64 machine and a car to the list price of vmware or
VirtualPC, and I think you've got yourself a bargain :-)
Paul
next prev parent reply other threads:[~2004-09-30 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 15:40 [Qemu-devel] qemu for x86_64 jmf
2004-09-30 16:06 ` Paul Brook [this message]
2004-09-30 16:42 ` [Qemu-devel] " Ben Pfaff
-- strict thread matches above, loose matches on Subject: below --
2004-09-29 23:27 [Qemu-devel] " jmf
[not found] ` <19692.1096532454@www70.gmx.net>
2004-09-30 8:49 ` Johannes Schindelin
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=200409301706.50083.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=jmfguy@excite.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).