From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, philmd@linaro.org, qemu-arm@nongnu.org
Subject: Re: [PATCH] target/arm: Two fixes for secure ptw
Date: Thu, 3 Nov 2022 13:23:55 +0000 [thread overview]
Message-ID: <CAFEAcA_dfNpVKWorvprdywGEaquDDVfdRf2-RJHrAm0aKYKeBA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_meGSRv=Fa1D-F=a3VF=TnHHORGAZoi5aPOkVAbGPm4w@mail.gmail.com>
On Thu, 3 Nov 2022 at 13:19, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Wed, 2 Nov 2022 at 05:47, Richard Henderson
> <richard.henderson@linaro.org> wrote:
> >
> > Reversed the sense of non-secure in get_phys_addr_lpae,
> > and failed to initialize attrs.secure for ARMMMUIdx_Phys_S.
> >
> > Fixes: 48da29e4 ("target/arm: Add ptw_idx to S1Translate")
> > Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1293
> > Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> > ---
> > target/arm/ptw.c | 15 ++++++++-------
> > 1 file changed, 8 insertions(+), 7 deletions(-)
> >
> > diff --git a/target/arm/ptw.c b/target/arm/ptw.c
> > index 58a7bbda50..df3573f150 100644
> > --- a/target/arm/ptw.c
> > +++ b/target/arm/ptw.c
> > @@ -1357,7 +1357,7 @@ static bool get_phys_addr_lpae(CPUARMState *env, S1Translate *ptw,
> > descaddr |= (address >> (stride * (4 - level))) & indexmask;
> > descaddr &= ~7ULL;
> > nstable = extract32(tableattrs, 4, 1);
> > - if (!nstable) {
> > + if (nstable) {
> > /*
> > * Stage2_S -> Stage2 or Phys_S -> Phys_NS
> > * Assert that the non-secure idx are even, and relative order.
> > @@ -2671,6 +2671,13 @@ static bool get_phys_addr_with_struct(CPUARMState *env, S1Translate *ptw,
> > bool is_secure = ptw->in_secure;
> > ARMMMUIdx s1_mmu_idx;
> >
> > + /*
> > + * The page table entries may downgrade secure to non-secure, but
> > + * cannot upgrade an non-secure translation regime's attributes
> > + * to secure.
> > + */
> > + result->f.attrs.secure = is_secure;
> > +
> > switch (mmu_idx) {
> > case ARMMMUIdx_Phys_S:
> > case ARMMMUIdx_Phys_NS:
> > @@ -2712,12 +2719,6 @@ static bool get_phys_addr_with_struct(CPUARMState *env, S1Translate *ptw,
> > break;
> > }
> >
> > - /*
> > - * The page table entries may downgrade secure to non-secure, but
> > - * cannot upgrade an non-secure translation regime's attributes
> > - * to secure.
> > - */
> > - result->f.attrs.secure = is_secure;
> > result->f.attrs.user = regime_is_user(env, mmu_idx);
>
> Do we also need to move this setting of attrs.user ?
> get_phys_addr_disabled() doesn't set that either.
I've applied this to target-arm.next for the moment anyway, since
it is definitely fixing an attrs.secure related bug. I can replace
that with a v2 or we can do a follow-on patch, depending whether
you get to this before or after I send out a pullreq.
thanks
-- PMM
next prev parent reply other threads:[~2022-11-03 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 5:47 [PATCH] target/arm: Two fixes for secure ptw Richard Henderson
2022-11-02 9:02 ` Philippe Mathieu-Daudé
2022-11-03 13:19 ` Peter Maydell
2022-11-03 13:23 ` Peter Maydell [this message]
2022-11-03 20:30 ` Richard Henderson
2022-11-04 10:58 ` Peter Maydell
2022-11-04 22:06 ` Richard Henderson
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_dfNpVKWorvprdywGEaquDDVfdRf2-RJHrAm0aKYKeBA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=philmd@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).