From: Anushree Mathur <anushree.mathur@linux.vnet.ibm.com>
To: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
richard.henderson@linaro.org, alex.bennee@linaro.org
Cc: Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Nicholas Piggin <npiggin@gmail.com>,
harshpb@linux.ibm.com
Subject: qemu-system-ppc64 option -smp 2 broken with commit 20b6643324a79860dcdfe811ffe4a79942bca21e
Date: Fri, 23 Jun 2023 16:39:52 +0530 [thread overview]
Message-ID: <8780abd9-59ef-c452-bfee-c3bfbf275e51@linux.vnet.ibm.com> (raw)
Hi everyone,
I was trying to boot rhel9.3 image with upstream qemu-system-ppc64 -smp
2 option and observed a segfault (qemu crash).
qemu command line used:
qemu-system-ppc64 -name Rhel9.3.ppc64le -smp 2 -m 16G -vga none
-nographic -machine pseries -cpu POWER10 -accel tcg -device
virtio-scsi-pci -drive file=/home/rh93.qcow2,if=none,format=qcow2,id=hd0
-device scsi-hd,drive=hd0 -boot c
After doing a git bisect, I found the first bad commit which introduced
this issue is below:
[qemu]# git bisect good
20b6643324a79860dcdfe811ffe4a79942bca21e is the first bad commit
commit 20b6643324a79860dcdfe811ffe4a79942bca21e
Author: Richard Henderson <richard.henderson@linaro.org>
Date: Mon Dec 5 17:45:02 2022 -0600
tcg/ppc: Reorg goto_tb implementation
The old ppc64 implementation replaces 2 or 4 insns, which leaves a race
condition in which a thread could be stopped at a PC in the middle of
the sequence, and when restarted does not see the complete address
computation and branches to nowhere.
The new implemetation replaces only one insn, swapping between
b <dest>
and
mtctr r31
falling through to a general-case indirect branch.
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
tcg/ppc/tcg-target.c.inc | 152
+++++++++++++----------------------------------
tcg/ppc/tcg-target.h | 3 +-
2 files changed, 41 insertions(+), 114 deletions(-)
[qemu]#
Can someone please take a look and suggest a fix to resolve this issue?
Thanks in advance.
Regards,
Anushree-Mathur
next reply other threads:[~2023-06-23 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 11:09 Anushree Mathur [this message]
2023-06-23 13:46 ` qemu-system-ppc64 option -smp 2 broken with commit 20b6643324a79860dcdfe811ffe4a79942bca21e Cédric Le Goater
2023-06-23 15:22 ` Alex Bennée
2023-07-12 8:34 ` Anushree Mathur
2023-06-26 5:17 ` Anushree Mathur
2023-06-26 6:18 ` Cédric Le Goater
2023-06-24 14:29 ` Michael Tokarev
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=8780abd9-59ef-c452-bfee-c3bfbf275e51@linux.vnet.ibm.com \
--to=anushree.mathur@linux.vnet.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=dbarboza@ventanamicro.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).