qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] 64-on-32 TCG broken


From: Stefan Weil
Subject: Re: [Qemu-devel] 64-on-32 TCG broken
Date: Tue, 30 Oct 2012 23:24:34 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121027 Iceowl/1.0b1 Icedove/3.0.11

Am 30.10.2012 09:15, schrieb Paolo Bonzini:
Il 29/10/2012 19:29, Aurelien Jarno ha scritto:
On Mon, Oct 29, 2012 at 06:53:14PM +0100, Paolo Bonzini wrote:
Known-good commit: 8473f377393219390ea6f2d8d450a2b054bb823e
Known-bad commit: d262cb02861dd33375c08fc798930653b14769e9

i386-softmmu seems to work.  I may try to bisect it tomorrow, but I'd be
glad if somebody else beats me.  It can be reproduced with Wine and
"x86_64-softmmu/qemu-system-x86_64.exe -L ../pc-bios"; it hangs at iPXE.
Oops, sorry about that. Is it win32 or win64? I'll try to fix it asap,
but right now I don't have a good network connection enough to either
setup a mingw build environment or to connect to a remote machine with
such an environment.

It's win32, and the first bad commit is 9c43b68 (tcg: rework liveness
analysis, 2012-10-09).  But it looks like 64-on-32 emulation is more
generally broken.  I now tried x86_64-linux-user compiled for 32-bit,
and it segfaults on startup.  Even the previous commit cannot run
qemu-x86_64 /bin/ls correctly:


I just tested with latest qemu-system-x86_64 on 32 bit Linux.

It also hangs during boot (BIOS), so it looks like this
is not a MinGW only problem.

Your test with x86_64-linux-user indicates that, too.

I also get the problem with TCI. Therefore I expect that any
32 bit TCG target will show it.

Regards
Stefan W.



$ git whatis HEAD
ec7a869 (tcg: sync output arguments on liveness request, 2012-10-09)
$ x86_64-linux-user/qemu-x86_64 /bin/ls
inux-user

$ git whatis HEAD
9c43b68 (tcg: rework liveness analysis, 2012-10-09)
$ x86_64-linux-user/qemu-x86_64 /bin/ls
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Errore di segmentazione


Regarding the win32 failure, it's early enough that the TCG logs give
an idea of what is happening.  This *might* be a reduced testcase,
but the general breakage makes it impossible to check:




reply via email to

[Prev in Thread] Current Thread [Next in Thread]