From: Anushree Mathur <anushree.mathur@linux.vnet.ibm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
richard.henderson@linaro.org,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Nicholas Piggin <npiggin@gmail.com>,
harshpb@linux.ibm.com
Subject: Re: qemu-system-ppc64 option -smp 2 broken with commit 20b6643324a79860dcdfe811ffe4a79942bca21e
Date: Wed, 12 Jul 2023 14:04:38 +0530 [thread overview]
Message-ID: <a213011e-9dc7-194f-47c2-696ee867e0f1@linux.vnet.ibm.com> (raw)
In-Reply-To: <87y1kadwqz.fsf@linaro.org>
Hi Alex,
On 6/23/23 20:52, Alex Bennée wrote:
> Cédric Le Goater <clg@kaod.org> writes:
>
>> Hello Anushree,
>>
>> On 6/23/23 13:09, Anushree Mathur wrote:
>>> 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:
>> Could you please open a gitlab issue on QEMU project ?
>>
>> https://gitlab.com/qemu-project/qemu/-/issues
> Is it broken generated code that faults or does the goto_tb code break
> the execution sequence in some subtle way further down the line?
>
> If you can isolate the guest address the output from:
>
> -dfilter 0xBADADDR+0x100 -d in_asm,op,out_asm
I tried as suggested above but didn't get much info collected.
I have shared my observation on the gitlab issue page.
https://gitlab.com/qemu-project/qemu/-/issues/1726
Thanks,
Anushree-Mathur
> would be useful for the bug report. Although conceivably the out_asm
> output might make sense at translation time and then be broken when it
> is patched. Having rr on power would be really useful to debug this sort
> of thing.
>
>> Thanks,
>>
>> C.
>>
>>> [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 prev parent reply other threads:[~2023-07-12 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 11:09 qemu-system-ppc64 option -smp 2 broken with commit 20b6643324a79860dcdfe811ffe4a79942bca21e Anushree Mathur
2023-06-23 13:46 ` Cédric Le Goater
2023-06-23 15:22 ` Alex Bennée
2023-07-12 8:34 ` Anushree Mathur [this message]
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=a213011e-9dc7-194f-47c2-696ee867e0f1@linux.vnet.ibm.com \
--to=anushree.mathur@linux.vnet.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=clg@kaod.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).