qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Romero <gustavo.romero@linaro.org>
To: Jim MacArthur <jim.macarthur@linaro.org>,
	qemu-devel@nongnu.org,
	Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH V4 2/4] target/arm: Allow writes to FNG1, FNG0, A2
Date: Tue, 2 Dec 2025 11:29:08 -0300	[thread overview]
Message-ID: <c2747a88-436d-41bf-8277-b1c10a1aafc5@linaro.org> (raw)
In-Reply-To: <20251202120250.763150-3-jim.macarthur@linaro.org>

Hi Jim,

On 12/2/25 09:00, Jim MacArthur wrote:
> This just allows read/write of three feature bits. ASID is still
> ignored. Any writes to TTBR0_EL0 and TTBR1_EL0, including changing
> the ASID, will still cause a complete flush of the TLB.
> 
> Signed-off-by: Jim MacArthur <jim.macarthur@linaro.org>
> ---
>   target/arm/cpu-features.h | 7 +++++++
>   target/arm/helper.c       | 6 ++++++
>   2 files changed, 13 insertions(+)
> 
> diff --git a/target/arm/cpu-features.h b/target/arm/cpu-features.h
> index 579fa8f8f4..d56bda9ce0 100644
> --- a/target/arm/cpu-features.h
> +++ b/target/arm/cpu-features.h
> @@ -346,6 +346,8 @@ FIELD(ID_AA64MMFR3, SDERR, 52, 4)
>   FIELD(ID_AA64MMFR3, ADERR, 56, 4)
>   FIELD(ID_AA64MMFR3, SPEC_FPACC, 60, 4)
>   
> +FIELD(ID_AA64MMFR4, ASID2, 8, 4)
> +
>   FIELD(ID_AA64DFR0, DEBUGVER, 0, 4)
>   FIELD(ID_AA64DFR0, TRACEVER, 4, 4)
>   FIELD(ID_AA64DFR0, PMUVER, 8, 4)
> @@ -1369,6 +1371,11 @@ static inline bool isar_feature_aa64_aie(const ARMISARegisters *id)
>       return FIELD_EX64_IDREG(id, ID_AA64MMFR3, AIE) != 0;
>   }
>   
> +static inline bool isar_feature_aa64_asid2(const ARMISARegisters *id)
> +{
> +    return FIELD_EX64_IDREG(id, ID_AA64MMFR4, ASID2) != 0;
> +}
> +
>   static inline bool isar_feature_aa64_mec(const ARMISARegisters *id)
>   {
>       return FIELD_EX64_IDREG(id, ID_AA64MMFR3, MEC) != 0;
> diff --git a/target/arm/helper.c b/target/arm/helper.c
> index c20334fa65..7812a82bab 100644
> --- a/target/arm/helper.c
> +++ b/target/arm/helper.c
> @@ -6102,6 +6102,9 @@ static void tcr2_el1_write(CPUARMState *env, const ARMCPRegInfo *ri,
>       if (cpu_isar_feature(aa64_aie, cpu)) {
>           valid_mask |= TCR2_AIE;
>       }
> +    if (cpu_isar_feature(aa64_asid2, cpu)) {
> +        valid_mask |= TCR2_FNG1 | TCR2_FNG0 | TCR2_A2;
> +    }
>       value &= valid_mask;
>       raw_write(env, ri, value);
>   }
> @@ -6121,6 +6124,9 @@ static void tcr2_el2_write(CPUARMState *env, const ARMCPRegInfo *ri,
>       if (cpu_isar_feature(aa64_mec, cpu)) {
>           valid_mask |= TCR2_AMEC0 | TCR2_AMEC1;
>       }
> +    if (cpu_isar_feature(aa64_asid2, cpu)) {
> +        valid_mask |= TCR2_FNG1 | TCR2_FNG0 | TCR2_A2;
> +    }
>       value &= valid_mask;
>       raw_write(env, ri, value);
>   }

Afaics, we are not flushing the TLB here like we do for TCR_ELx (in vmsa_tcr_el12_write) before
we call raw_write(). Since here we could be changing the A2 & friends bits, which can change
the value of the ASID being using (like the TCR_ELx.A1 bit), I believe we should flush the TLB
explicitly here like we do in vmsa_tcr_el12_write().

@rth wdyt?


Cheers,
Gustavo


  reply	other threads:[~2025-12-02 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 12:00 [PATCH V4 0/4] Basic ASID2 Support Jim MacArthur
2025-12-02 12:00 ` [PATCH V4 1/4] target/arm: Enable ID_AA64MMFR4_EL1 register Jim MacArthur
2025-12-02 14:28   ` Gustavo Romero
2025-12-02 12:00 ` [PATCH V4 2/4] target/arm: Allow writes to FNG1, FNG0, A2 Jim MacArthur
2025-12-02 14:29   ` Gustavo Romero [this message]
2025-12-04 16:25     ` Jim MacArthur
2025-12-02 12:00 ` [PATCH V4 3/4] target/arm/tcg/cpu64.c: Enable ASID2 for cpu_max Jim MacArthur
2025-12-02 14:29   ` Gustavo Romero
2025-12-02 12:00 ` [PATCH V4 4/4] tests: Add test for ASID2 and write/read of feature bits Jim MacArthur
2025-12-02 14:30   ` Gustavo Romero

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=c2747a88-436d-41bf-8277-b1c10a1aafc5@linaro.org \
    --to=gustavo.romero@linaro.org \
    --cc=jim.macarthur@linaro.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).