qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] 64-on-32 TCG broken
Date: Tue, 30 Oct 2012 23:24:34 +0100	[thread overview]
Message-ID: <509053A2.6010504@weilnetz.de> (raw)
In-Reply-To: <508F8CBB.8090101@redhat.com>

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	other threads:[~2012-10-30 22:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 17:53 [Qemu-devel] x86_64-softmmu broken on Windows (TCG?) Paolo Bonzini
2012-10-29 18:29 ` Aurelien Jarno
2012-10-30  8:15   ` [Qemu-devel] 64-on-32 TCG broken [was Re: x86_64-softmmu broken on Windows (TCG?)] Paolo Bonzini
2012-10-30 22:24     ` Stefan Weil [this message]
2012-10-30 23:22       ` [Qemu-devel] 64-on-32 TCG broken Aurelien Jarno
2012-10-30 23:56       ` Aurelien Jarno
2012-10-31 12:40         ` Aurelien Jarno
2012-10-31 14:01           ` Paolo Bonzini
2012-10-31 14:05             ` Peter Maydell
2012-10-31 14:08               ` Paolo Bonzini
2012-10-31 15:23                 ` Aurelien Jarno
2012-10-31 17:05         ` Stefan Weil
2012-10-31 21:48           ` Aurelien Jarno
2012-11-07 13:26         ` Kirill Batuzov
2012-11-11 16:05           ` Aurelien Jarno

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=509053A2.6010504@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=aurelien@aurel32.net \
    --cc=pbonzini@redhat.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).