From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v4 4/4] meson: Warn when TCI is selected but TCG backend is available
Date: Wed, 27 Jan 2021 21:47:50 +0000 [thread overview]
Message-ID: <87tur2vyif.fsf@linaro.org> (raw)
In-Reply-To: <d265dadc-45e8-3813-4e2d-cde007c389ac@weilnetz.de>
Stefan Weil <sw@weilnetz.de> writes:
> Am 27.01.21 um 20:52 schrieb Alex Bennée:
>
>> For example - debian-buster (arm64) running ffmpeg:
>>
>> alex.bennee@8cd150a4b35d:~/lsrc/qemu.git/builds/all.tci$ ./qemu-aarch64 /usr/bin/ffmpeg -i theora.mkv theora.webm
>> TODO ../../tcg/tci.c:882: tcg_qemu_tb_exec()
>> ../../tcg/tci.c:882: tcg fatal error
>> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
>> Segmentation fault (core dumped)
>
>
> Thanks. All I tried to say is that I prefer to replace those TODO
> statements by working code as soon as there was a case which triggers
> them. Most of those TODO statements are very easy to implement, so
> anyone can add them when he/she detects a missing one. If I get
> information about a scenario which triggers a missing TODO, I'll fix
> that of course. I just don't want to add that missing code blindly.
Your just going to end up playing wack-a-mole:
TODO ../../tcg/tci.c:620: tcg_qemu_tb_exec()me=00:00:00.00 bitrate=N/A speed= 0x
../../tcg/tci.c:620: tcg fatal error
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
> Using `make check-tcg` helped finding and fixing one of them, future
> improved CI checks can find more, and so can examples like the one
> above. The error message tci.c:882 is INDEX_op_ld8s_i64
> (https://github.com/qemu/qemu/blob/master/tcg/tci.c#L882). The missing
> code is nearly identical to the existing code for INDEX_op_ld8u_i64, but
> with *(int8_t *) instead of *(uint8_t *), so maybe you can try that and
> confirm whether it fixes the reported problem. Otherwise I'll try to
> reproduce it with any mkv file.
ffmpeg is a good application for working out the SIMD code because it
features quite a lot of optimised code for each architecture.
> I recently tried running tesseract with qemu-x86_64 because I had
> expected that it might trigger some unimplemented TCG opcodes.
qemu-x86-64 is a poor choice as a relatively under maintained front-end
doesn't emulate a particularly new CPU or take advantage of the new TCG
features. ARM64 is pretty good because the default cpu for linux-user is
CPU max which a) enables all ISA features we have and b) exposes them
fairly easily to guest detection routines which probe feature registers.
> Instead
> it showed a general problem for native TCG: qemu-x86_64 allocates too
> much memory for tesseract and gets killed by the Linux kernel OOM
> handler.
Do you have a command line? That sounds like something that should be
fixed.
>
> Regards,
>
> Stefan
--
Alex Bennée
next prev parent reply other threads:[~2021-01-27 21:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 14:45 [PATCH v4 0/4] meson: Try to clarify TCG / TCI options for new users Philippe Mathieu-Daudé
2021-01-25 14:45 ` [PATCH v4 1/4] configure: Fix --enable-tcg-interpreter Philippe Mathieu-Daudé
2021-01-25 16:36 ` Paolo Bonzini
2021-01-25 17:10 ` Daniel P. Berrangé
2021-01-26 19:46 ` Stefan Weil
2021-01-25 14:45 ` [PATCH v4 2/4] configure: Improve TCI feature description Philippe Mathieu-Daudé
2021-01-25 16:44 ` Daniel P. Berrangé
2021-01-25 14:45 ` [PATCH v4 3/4] meson: Explicit TCG backend used Philippe Mathieu-Daudé
2021-01-25 16:45 ` Daniel P. Berrangé
2021-01-25 14:45 ` [PATCH v4 4/4] meson: Warn when TCI is selected but TCG backend is available Philippe Mathieu-Daudé
2021-01-25 16:46 ` Daniel P. Berrangé
2021-01-25 16:47 ` Daniel P. Berrangé
2021-01-25 17:05 ` Philippe Mathieu-Daudé
2021-01-25 18:58 ` Stefan Weil
2021-01-25 19:02 ` Richard Henderson
2021-01-25 21:02 ` Stefan Weil
2021-01-25 22:35 ` Richard Henderson
2021-01-26 11:40 ` Stefan Weil
2021-01-26 17:24 ` Alex Bennée
2021-01-26 19:44 ` Stefan Weil
2021-01-26 20:07 ` Paolo Bonzini
2021-01-26 20:10 ` Stefan Weil
2021-01-26 22:39 ` Richard Henderson
2021-01-27 6:53 ` Stefan Weil
2021-01-27 17:19 ` Richard Henderson
2021-01-27 19:52 ` Alex Bennée
2021-01-27 20:49 ` Stefan Weil
2021-01-27 21:47 ` Alex Bennée [this message]
2021-01-28 2:49 ` Stefan Weil
2021-01-28 6:51 ` qemu user mode fails to run programs with large VM / built with address sanitizer (was: Re: [PATCH v4 4/4] meson: Warn when TCI is selected but TCG backend is available) Stefan Weil
2021-01-28 8:29 ` Richard Henderson
2021-01-27 10:02 ` [PATCH v4 4/4] meson: Warn when TCI is selected but TCG backend is available Daniel P. Berrangé
2021-01-27 12:34 ` Alex Bennée
2021-01-26 10:34 ` Daniel P. Berrangé
2021-01-29 8:06 ` [PATCH v4 0/4] meson: Try to clarify TCG / TCI options for new users Paolo Bonzini
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=87tur2vyif.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sw@weilnetz.de \
--cc=thuth@redhat.com \
/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).