From: David Hildenbrand <david@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: s390x/qemu-user: TODO /home/dhildenb/git/qemu/tcg/tci.c:859: tcg_qemu_tb_exec()
Date: Thu, 17 Oct 2019 12:35:32 +0200 [thread overview]
Message-ID: <2f96242c-7108-f9a6-0a1a-fdef3eee2a47@redhat.com> (raw)
In-Reply-To: <95ddf722-ba5d-dd48-a840-0d940ded3acd@redhat.com>
On 17.10.19 12:25, Philippe Mathieu-Daudé wrote:
> Hi David,
>
> On 10/17/19 12:02 PM, David Hildenbrand wrote:
>> Hi,
>>
>> I'm currently trying to run Fedora 31 under qemu-user
>> (https://github.com/fedora-cloud/docker-brew-fedora/tree/8a81f67271e959dfc8f8a888b161bbd540b7a83b/s390x)
>> in order to debug a vector instruction issue.
>>
>> Strangely, when trying to chroot into above rootfs and running
>> /bin/bash, I get
>>
>> t460s: ~/f31 $ sudo chroot . ./qemu-s390x /bin/bash
>> TODO /home/dhildenb/git/qemu/tcg/tci.c:859: tcg_qemu_tb_exec()
>> /home/dhildenb/git/qemu/tcg/tci.c:859: tcg fatal error
>> Aborted
>>
>>
>> But it's not fundamentally broken:
>>
>> t460s: ~/f31 $ sudo chroot . ./qemu-s390x /bin/ls
>> bin dev home lib64 media opt qemu-s390x run srv tmp var
>> boot etc lib lost+found mnt proc root sbin sys usr
>>
>>
>> I do wonder why we don't run into the same issue under qemu-systems390x.
>
> Are you also using TCI in system emulation?
Most probably not. It took me longer than expected to find a ./configure
variant that at least allows me to build static qemu-user binaries. Most
probably something sneeked in there.
>
> Can you simply use TCG to debug your vector instruction issue instead?
I was using
./configure --disable-strip --disable-werror --python=/usr/bin/python3
--enable-tcg-interpreter --disable-system --enable-linux-user --static
--disable-pie --disable-sdl --disable-gtk --disable-spice
--disable-tools --disable-guest-agent --disable-guest-agent-msi
--disable-curses --disable-curl --disable-gnutls --disable-gcrypt
--disable-nettle --disable-cap-ng --disable-brlapi --disable-mpath
--disable-capstone --disable-xen --disable-rdma
--extra-ldflags="-Wl,-z,relro -Wl,-z,now" --target-list=s390x-linux-user
inspired by the Fedora rpm SPEC.
"--enable-tcg-interpreter" is the relevant bit I blindly copied without
thinking about it (in the rpm SPEC, it is wrapped by an ifdef ...)
Thanks for the hint, will try with --disable-tcg-interpreter
>
> Regards,
>
> Phil.
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-10-17 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 10:02 s390x/qemu-user: TODO /home/dhildenb/git/qemu/tcg/tci.c:859: tcg_qemu_tb_exec() David Hildenbrand
2019-10-17 10:25 ` Philippe Mathieu-Daudé
2019-10-17 10:35 ` David Hildenbrand [this message]
2019-10-17 10:42 ` Philippe Mathieu-Daudé
2019-10-17 11:01 ` Thomas Huth
2019-10-21 16:37 ` Richard Henderson
2019-10-21 16:40 ` Peter Maydell
2019-10-21 16:48 ` Richard Henderson
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=2f96242c-7108-f9a6-0a1a-fdef3eee2a47@redhat.com \
--to=david@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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).