From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>
Subject: Re: [PATCH for-8.1 3/3] target/arm/ptw.c: Account for FEAT_RME when applying {N}SW,SA bits
Date: Thu, 13 Jul 2023 19:31:19 +0100 [thread overview]
Message-ID: <fa2d89b7-8bfa-997a-dcf3-75fdb2ad3b46@linaro.org> (raw)
In-Reply-To: <20230710152130.3928330-4-peter.maydell@linaro.org>
On 7/10/23 16:21, Peter Maydell wrote:
> In get_phys_addr_twostage() the code that applies the effects of
> VSTCR.{SA,SW} and VTCR.{NSA,NSW} only updates result->f.attrs.secure.
> Now we also have f.attrs.space for FEAT_RME, we need to keep the two
> in sync.
>
> These bits only have an effect for Secure space translations, not
> for Root, so use the input in_space field to determine whether to
> apply them rather than the input is_secure. This doesn't actually
> make a difference because Root translations are never two-stage,
> but it's a little clearer.
>
> Signed-off-by: Peter Maydell<peter.maydell@linaro.org>
> ---
> I noticed this while reading through the ptw code...
> ---
> target/arm/ptw.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2023-07-13 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 15:21 [PATCH for-8.1 0/3] target/arm: Fix ptw bugs introduced by FEAT_RME changes Peter Maydell
2023-07-10 15:21 ` [PATCH for-8.1 1/3] target/arm/ptw.c: Add comments to S1Translate struct fields Peter Maydell
2023-07-13 17:37 ` Richard Henderson
2023-07-10 15:21 ` [PATCH for-8.1 2/3] target/arm: Fix S1_ptw_translate() debug path Peter Maydell
2023-07-10 16:46 ` Peter Maydell
2023-07-11 11:05 ` Jean-Philippe Brucker
2023-07-13 18:28 ` Richard Henderson
2023-07-10 15:21 ` [PATCH for-8.1 3/3] target/arm/ptw.c: Account for FEAT_RME when applying {N}SW, SA bits Peter Maydell
2023-07-13 18:31 ` Richard Henderson [this message]
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=fa2d89b7-8bfa-997a-dcf3-75fdb2ad3b46@linaro.org \
--to=richard.henderson@linaro.org \
--cc=jean-philippe@linaro.org \
--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).