[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 7/7] target/arm: Add CPU properties for most v8.3 PAC feat
From: |
Peter Maydell |
Subject: |
Re: [PATCH v2 7/7] target/arm: Add CPU properties for most v8.3 PAC features |
Date: |
Fri, 24 Feb 2023 11:23:54 +0000 |
On Wed, 22 Feb 2023 at 22:14, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> On 2/22/23 09:35, Aaron Lindsay wrote:
> > Signed-off-by: Aaron Lindsay <aaron@os.amperecomputing.com>
> > ---
> > +static Property arm_cpu_pauth2_property =
> > + DEFINE_PROP_BOOL("pauth2", ARMCPU, prop_pauth2, false);
> > +static Property arm_cpu_pauth_fpac_property =
> > + DEFINE_PROP_BOOL("pauth-fpac", ARMCPU, prop_pauth_fpac, false);
> > +static Property arm_cpu_pauth_fpac_combine_property =
> > + DEFINE_PROP_BOOL("pauth-fpac-combine", ARMCPU,
> > prop_pauth_fpac_combine, false);
>
> For -cpu max, I would expect these to default on.
> Or perhaps not expose these or epac as properties at all.
Yes; unless there's a reason why we want the properties, we
shouldn't bother defining them. As Richard says, having
a 'pauth' property is a special case where we needed to be
able to avoid the massive extra emulation overhead of doing
it per the architected algorithm.
thanks
-- PMM
- [PATCH v2 0/7] Implement Most ARMv8.3 Pointer Authentication Features, Aaron Lindsay, 2023/02/22
- [PATCH v2 4/7] target/arm: Implement v8.3 Pauth2, Aaron Lindsay, 2023/02/22
- [PATCH v2 3/7] target/arm: Implement v8.3 EnhancedPAC, Aaron Lindsay, 2023/02/22
- [PATCH v2 5/7] targer/arm: Inform helpers whether a PAC instruction is 'combined', Aaron Lindsay, 2023/02/22
- [PATCH v2 7/7] target/arm: Add CPU properties for most v8.3 PAC features, Aaron Lindsay, 2023/02/22
- [PATCH v2 2/7] target/arm: Implement v8.3 QARMA3 PAC cipher, Aaron Lindsay, 2023/02/22
- [PATCH v2 1/7] target/arm: v8.3 PAC ID_AA64ISAR[12] feature-detection, Aaron Lindsay, 2023/02/22
- [PATCH v2 6/7] target/arm: Implement v8.3 FPAC and FPACCOMBINE, Aaron Lindsay, 2023/02/22