From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CliPn-0000ZT-Qr for qemu-devel@nongnu.org; Tue, 04 Jan 2005 01:43:35 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CliPl-0000YG-Oe for qemu-devel@nongnu.org; Tue, 04 Jan 2005 01:43:34 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CliPl-0000Y6-LS for qemu-devel@nongnu.org; Tue, 04 Jan 2005 01:43:33 -0500 Received: from [80.91.229.2] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CliEN-0003UW-5X for qemu-devel@nongnu.org; Tue, 04 Jan 2005 01:31:47 -0500 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CliEM-0001kA-00 for ; Tue, 04 Jan 2005 07:31:46 +0100 Received: from inet.ycc.ru ([217.148.52.177]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Jan 2005 07:31:45 +0100 Received: from patrakov by inet.ycc.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Jan 2005 07:31:45 +0100 From: "Alexander E. Patrakov" Date: Tue, 04 Jan 2005 11:31:48 +0500 Message-ID: References: <41D9E0BB.1070202@bellard.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="nextPart2542994.OeYM5gQL1t" Content-Transfer-Encoding: 7Bit Sender: news Subject: [Qemu-devel] Re: x86_64 target Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --nextPart2542994.OeYM5gQL1t Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8Bit 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 --nextPart2542994.OeYM5gQL1t Content-Type: text/plain; name="crash.txt" Content-Transfer-Encoding: 7Bit Content-Disposition: attachment; filename="crash.txt" *** 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. --nextPart2542994.OeYM5gQL1t--