From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH 2/2] target/arm: Fix unaligned mte checks
Date: Fri, 2 Apr 2021 18:35:16 +0000 [thread overview]
Message-ID: <CAFEAcA-jky04K9d3WFxj+JU31mP_NS+yrEDXzXaffYC7CRTFLQ@mail.gmail.com> (raw)
In-Reply-To: <20210402053728.265173-3-richard.henderson@linaro.org>
On Fri, 2 Apr 2021 at 06:42, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> We were incorrectly assuming that only the first byte of an MTE access
> is checked against the tags. But per the ARM, unaligned accesses are
> pre-decomposed into single-byte accesses. So by the time we reach the
> actual MTE check in the ARM pseudocode, all accesses are aligned.
>
> Therefore, drop mte_check1, since we cannot know a priori that an
> access is aligned. Rename mte_checkN to mte_check, which now handles
> all accesses. Rename mte_probe1 to mte_probe, and use a common helper.
>
> Drop the computation of the faulting nth element, since all accesses
> can be considered to devolve to bytes, and simply compute the faulting
> address.
>
> Buglink: https://bugs.launchpad.net/bugs/1921948
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
This is a pretty chunky patch for this point in the release cycle.
I don't suppose there's a way to make it more digestible for review?
thanks
-- PMM
next prev parent reply other threads:[~2021-04-02 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 5:37 [PATCH 0/2] target/arm: Fix unaligned mte checks Richard Henderson
2021-04-02 5:37 ` [PATCH 1/2] target/arm: Check PAGE_WRITE_ORG for MTE writeability Richard Henderson
2021-04-02 5:37 ` [PATCH 2/2] target/arm: Fix unaligned mte checks Richard Henderson
2021-04-02 15:43 ` Richard Henderson
2021-04-02 18:35 ` Peter Maydell [this message]
2021-04-02 18:44 ` Richard Henderson
2021-04-02 5:45 ` [PATCH 0/2] " no-reply
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=CAFEAcA-jky04K9d3WFxj+JU31mP_NS+yrEDXzXaffYC7CRTFLQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@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).