From: Richard Henderson <richard.henderson@linaro.org>
To: Nikita Novikov <n.novikov@syntacore.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: Re: [PATCH] accel/tcg: Pass actual memop_size to tlb_fill instead of 0
Date: Wed, 22 Oct 2025 10:32:31 -0500 [thread overview]
Message-ID: <79beaf9a-9558-40e7-a01d-5f80d8931eba@linaro.org> (raw)
In-Reply-To: <20251022115213.91457-1-n.novikov@syntacore.com>
On 10/22/25 06:52, Nikita Novikov wrote:
> Recent debugging of misaligned access handling on RISC-V revealed that we
> always call `tlb_fill` with `memop_size == 0`. This behavior effectively
> disables natural alignment checks in `riscv_tlb_fill_align()`, because we
> have to fall back from `memop_size` to `size` when computing the alignment bits.
>
> With `memop_size == 0`, misaligned cross-page stores end up reported as
> `store access fault` (AF, cause=7) instead of the expected
> `store page fault` (PF, cause=15), since the “misalign” path triggers before
> the second page translation can fault. This breaks misaligned accesses at
> page boundaries.
>
> After switching to pass the real `l->memop` into `tlb_fill`, the cross-page
> faults are no longer mis-classified as AF.
>
> Fixes: ec03dd972378 ("accel/tcg: Hoist first page lookup above pointer_wrap")
>
> Signed-off-by: Nikita Novikov <n.novikov@syntacore.com>
> ---
> accel/tcg/cputlb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/accel/tcg/cputlb.c b/accel/tcg/cputlb.c
> index 631f1fe135..271c061be1 100644
> --- a/accel/tcg/cputlb.c
> +++ b/accel/tcg/cputlb.c
> @@ -1782,7 +1782,7 @@ static bool mmu_lookup(CPUState *cpu, vaddr addr, MemOpIdx oi,
> * If the lookup potentially resized the table, refresh the
> * first CPUTLBEntryFull pointer.
> */
> - if (mmu_lookup1(cpu, &l->page[1], 0, l->mmu_idx, type, ra)) {
> + if (mmu_lookup1(cpu, &l->page[1], l->memop, l->mmu_idx, type, ra)) {
> uintptr_t index = tlb_index(cpu, l->mmu_idx, addr);
> l->page[0].full = &cpu->neg.tlb.d[l->mmu_idx].fulltlb[index];
> }
How is the memop really applicable to the second half of a split-page operation?
r~
next prev parent reply other threads:[~2025-10-22 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 11:52 [PATCH] accel/tcg: Pass actual memop_size to tlb_fill instead of 0 Nikita Novikov
2025-10-22 15:24 ` Philippe Mathieu-Daudé
2025-10-22 15:32 ` Richard Henderson [this message]
2025-10-22 18:59 ` Nikita Novikov
2025-10-22 19:20 ` Richard Henderson
2025-10-23 6:38 ` Nikita Novikov
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=79beaf9a-9558-40e7-a01d-5f80d8931eba@linaro.org \
--to=richard.henderson@linaro.org \
--cc=n.novikov@syntacore.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).