From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: qemu-devel@nongnu.org
Cc: berrange@redhat.com,
Richard Henderson <richard.henderson@linaro.org>,
laurent@vivier.eu
Subject: qemu-user self emulation broken with default CPU on x86/x64
Date: Mon, 3 Jul 2023 18:03:08 +0200 [thread overview]
Message-ID: <c0a35ed3-7e4a-aea6-a3bd-9f0e4079f4e0@linaro.org> (raw)
Hi everyone,
Recently (in d135f781 [1], between v7.0.0 and v8.0.0), qemu-user default
cpu was updated to "max" instead of qemu32/qemu64.
This change "broke" qemu self emulation if this new default cpu is used.
$ ./qemu-x86_64 ./qemu-x86_64 --version
qemu-x86_64: ../util/cacheflush.c:212: init_cache_info: Assertion
`(isize & (isize - 1)) == 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted
By setting cpu back to qemu64, it works again.
$ ./qemu-x86_64 -cpu qemu64 ./qemu-x86_64 --version
qemu-x86_64 version 8.0.50 (v8.0.0-2317-ge125b08ed6)
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
Commenting assert does not work, as qemu aligned malloc fail shortly after.
I'm willing to fix it, but I'm not sure what is the issue with "max" cpu
exactly. Is it missing CPU cache line, or something else?
Any guidance would be welcome.
I know it's not the most important problem on earth, but it's still
surprising to meet this when you try to use qemu to emulate itself.
Regards,
Pierrick
[1]
https://gitlab.com/qemu-project/qemu/-/commit/d135f781405f7c78153aa65e0327b05a4aa72e50
next reply other threads:[~2023-07-03 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 16:03 Pierrick Bouvier [this message]
2023-07-03 18:04 ` qemu-user self emulation broken with default CPU on x86/x64 Daniel P. Berrangé
2023-07-03 21:05 ` GLibC AMD CPUID cache reporting regression (was Re: qemu-user self emulation broken with default CPU on x86/x64) Daniel P. Berrangé
2023-07-04 17:30 ` Pierrick Bouvier
2023-07-04 17:37 ` Florian Weimer
2023-07-05 13:08 ` Karumanchi, Sajan
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=c0a35ed3-7e4a-aea6-a3bd-9f0e4079f4e0@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=berrange@redhat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@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).