From: "Alex Bennée" <alex.bennee@linaro.org>
To: Jessica Clarke <jrtc27@jrtc27.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
"open list:ARM TCG CPUs" <qemu-arm@nongnu.org>
Subject: Re: [PATCH v3] target/arm: handle unaligned PC during tlb probe
Date: Fri, 05 Dec 2025 09:28:58 +0000 [thread overview]
Message-ID: <87fr9ps2ed.fsf@draig.linaro.org> (raw)
In-Reply-To: <aTI1VZHxicpycoLj@Jessicas-MacBook-Pro> (Jessica Clarke's message of "Fri, 5 Dec 2025 01:28:53 +0000")
Jessica Clarke <jrtc27@jrtc27.com> writes:
> On Thu, Dec 04, 2025 at 08:35:40PM +0000, Alex Bennée wrote:
>> PC alignment faults have priority over instruction aborts and we have
>> code to deal with this in the translation front-ends. However during
>> tb_lookup we can see a potentially faulting probe which doesn't get a
>> MemOp set. If the page isn't available this results in
>> EC_INSNABORT (0x20) instead of EC_PCALIGNMENT (0x22).
>>
>> As there is no easy way to set the appropriate MemOp in the
>> instruction fetch probe path lets just detect it in
>> arm_cpu_tlb_fill_align() ahead of the main alignment check. We also
>> teach arm_deliver_fault to deliver the right syndrome for
>> MMU_INST_FETCH alignment issues.
>>
>> Fixes: https://gitlab.com/qemu-project/qemu/-/issues/3233
>> Tested-by: Jessica Clarke <jrtc27@jrtc27.com>
>
> v3 is different enough from the tested RFC that maybe this shouldn't
> have been carried forwards, but I've now tested this v3 and it does
> indeed still fix the issue in my testing.
I did re-test myself and figured it was only adding to the robustness
but thanks for re-confirming its working for you.
>
> Thanks,
> Jessica
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-12-05 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 20:35 [PATCH v3] target/arm: handle unaligned PC during tlb probe Alex Bennée
2025-12-05 1:28 ` Jessica Clarke
2025-12-05 9:28 ` Alex Bennée [this message]
2025-12-05 15:11 ` Richard Henderson
2025-12-10 10:14 ` Michael Tokarev
2025-12-10 11:00 ` Alex Bennée
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=87fr9ps2ed.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=jrtc27@jrtc27.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).