From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: x86_64 target
Date: Tue, 04 Jan 2005 11:31:48 +0500 [thread overview]
Message-ID: <crdd85$jj4$1@sea.gmane.org> (raw)
In-Reply-To: 41D9E0BB.1070202@bellard.org
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Fabrice Bellard wrote:
> Hi,
>
> As a small gift for this new year, here is an initial implementation of
> the x86_64 target in QEMU. It is a "work in progress" as usual, but it
> works enough to boot an x86_64 Linux kernel (I used the one available at
> http://bochs.sourceforge.net/guestos/linux.x86-64.bzImage).
>
> Although the x86_64 target works correctly on 32 bit hosts, it is
> designed to have the best performances on 64 bit hosts, such as x86_64
> or ppc64. The current speed is poor relatively to the i386 emulation
> because I did not enable register usage on 64 bit hosts (no time to test
> it yet).
>
> The biggest missing part is a full implementation of SSE - I only added
> the minimal subset for the Linux kernel. I won't work again on the
> x86_64 target in the near future (as I said earlier most of my time is
> dedicated on improving the x86 on x86 speed), but anyone is free to
> submit patches.
I booted an existing win2k image with the new qemu-system-x86_64 emulator
(just to check that there are no i386 regressions) and the result is a
bluescreen (GOCR'ed and attached).
--
Alexander E. Patrakov
[-- Attachment #2: crash.txt --]
[-- Type: text/plain, Size: 860 bytes --]
*** STOP: 0x0000001E (0xC000001D,0x80432AC9,0xE1008A98,0xF74lB99C)
KMODE_EXCEPTION_NOT_HANDLED
*** Address 80432AC9 base at 80400000, DateStamp 384d9bl7 - ntoskrnl.exe
If this is the first time gou've seen this Stop error screen,
restart gour computer. If this screen appears again, follow
these steps:
Check to be sure gou have adequate disk space. If a driver is
identified in the Stop Message, disable the driver or check
with the manufacturer for driver updates. Try changing video
adapters.
Check with gour hardware vendor for ang BIOS updates. Disable
BIOS memorg options such as caching or shadowing. If gou need
to use Safe Mode to reMove or disable components, restart gour
computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
Refer to gour Getting Started manual for more information on
troubleshooting Stop errors.
next prev parent reply other threads:[~2005-01-04 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 0:18 [Qemu-devel] x86_64 target Fabrice Bellard
2005-01-04 2:15 ` Karl Magdsick
2005-01-04 14:29 ` Paul Brook
2005-01-05 17:48 ` Jeebs
2005-01-04 6:31 ` Alexander E. Patrakov [this message]
2005-01-04 19:56 ` [Qemu-devel] " Fabrice Bellard
2005-01-06 12:10 ` [Qemu-devel] " Lennert Buytenhek
2005-01-06 12:42 ` Lennert Buytenhek
2005-01-17 17:54 ` [Qemu-devel] " Ronald
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='crdd85$jj4$1@sea.gmane.org' \
--to=patrakov@ums.usu.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).