From: "Cédric Le Goater" <clegoate@redhat.com>
To: "Cédric Le Goater" <clg@kaod.org>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Howard Spoelstra" <hsp.cat7@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Nicholas Piggin <npiggin@gmail.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
BALATON Zoltan <balaton@eik.bme.hu>,
Harsh Prateek Bora <harshpb@linux.ibm.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
David Gibson <david@gibson.dropbear.id.au>,
Greg Kurz <groug@kaod.org>,
Frederic Barrat <frederic.barrat@fr.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH 0/4] target/ppc: Catch invalid real address accesses
Date: Wed, 28 Jun 2023 09:17:07 +0200 [thread overview]
Message-ID: <2bc2ca94-c1ba-a9de-0b81-6f9d3d4ad333@redhat.com> (raw)
In-Reply-To: <7e596b48-c631-34d5-2b63-0aac1922de93@kaod.org>
>>>> qemu-system-ppc.exe -M mac99,via=pmu -cdrom C:\mac-iso\9.2.2.iso -boot d -L pc-bios
>>>> crashes Mac OS with an address error. (with unpatched and patched builds).
>>>
>>> Same on Linux. I get an invalid opcode. QEMU 7.2 work fine though.
>>>
>>> C.
>>
>> That certainly shouldn't happen, and if it worked in 7.2 then there's definitely a regression which has crept in there somewhere. I'll try and bisect this at some point soon, but feel free to try and beat me ;)
>
> bisect points to :
>
> commit e506ad6a05c806bbef460a7d014a184ff8d707a6
> Author: Richard Henderson <richard.henderson@linaro.org>
> Date: Mon Mar 6 04:30:11 2023 +0300
>
> accel/tcg: Pass last not end to tb_invalidate_phys_range
> Pass the address of the last byte to be changed, rather than
> the first address past the last byte. This avoids overflow
> when the last page of the address space is involved.
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>
> include/exec/exec-all.h | 2 +-
> accel/tcg/tb-maint.c | 31 ++++++++++++++++---------------
> accel/tcg/translate-all.c | 2 +-
> accel/tcg/user-exec.c | 2 +-
> softmmu/physmem.c | 2 +-
> 5 files changed, 20 insertions(+), 19 deletions(-)
>
>
> I think the instruction is fnmadds. Needs more digging.
the invalid opcode is just a symptom of something bad happening.
C.
next prev parent reply other threads:[~2023-06-28 7:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 8:19 [PATCH 0/4] target/ppc: Catch invalid real address accesses Nicholas Piggin
2023-06-23 8:19 ` [PATCH 1/4] target/ppc: Machine check on invalid real address access Nicholas Piggin
2023-06-23 8:19 ` [PATCH 2/4] target/ppc: Add POWER9/10 invalid-real machine check codes Nicholas Piggin
2023-06-23 8:19 ` [PATCH 3/4] target/ppc: Move common check in machne check handlers to a function Nicholas Piggin
2023-06-23 13:20 ` Fabiano Rosas
2023-06-23 16:16 ` BALATON Zoltan
2023-06-25 9:20 ` Nicholas Piggin
2023-06-23 8:19 ` [PATCH 4/4] target/ppc: Make checkstop stop the system Nicholas Piggin
2023-06-23 11:51 ` BALATON Zoltan
2023-06-25 9:15 ` Nicholas Piggin
2023-06-23 9:10 ` [PATCH 0/4] target/ppc: Catch invalid real address accesses Peter Maydell
2023-06-23 12:37 ` Cédric Le Goater
2023-06-23 23:35 ` Philippe Mathieu-Daudé
2023-06-24 9:50 ` BALATON Zoltan
2023-06-26 13:35 ` Cédric Le Goater
2023-06-26 23:28 ` Nicholas Piggin
2023-06-27 6:49 ` Cédric Le Goater
2023-06-27 8:14 ` Mark Cave-Ayland
2023-06-27 10:28 ` Howard Spoelstra
2023-06-27 11:24 ` Mark Cave-Ayland
2023-06-27 12:05 ` Howard Spoelstra
2023-06-27 12:41 ` Cédric Le Goater
2023-06-27 20:26 ` Mark Cave-Ayland
2023-06-28 7:02 ` Cédric Le Goater
2023-06-28 7:17 ` Cédric Le Goater [this message]
2023-06-29 8:29 ` Mark Cave-Ayland
2023-06-29 9:05 ` Cédric Le Goater
2023-06-29 9:41 ` Nicholas Piggin
2023-06-27 12:03 ` Cédric Le Goater
2023-06-27 20:24 ` Mark Cave-Ayland
2023-06-25 9:18 ` Nicholas Piggin
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=2bc2ca94-c1ba-a9de-0b81-6f9d3d4ad333@redhat.com \
--to=clegoate@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=christophe.leroy@csgroup.eu \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=frederic.barrat@fr.ibm.com \
--cc=groug@kaod.org \
--cc=harshpb@linux.ibm.com \
--cc=hsp.cat7@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=npiggin@gmail.com \
--cc=peter.maydell@linaro.org \
--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).