From: Gustavo Romero <gustavo.romero@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
alex.bennee@linaro.org, peter.maydell@linaro.org
Subject: Re: [PATCH] target/arm: Enable FEAT_CMOW for -cpu max
Date: Mon, 4 Nov 2024 11:36:30 -0300 [thread overview]
Message-ID: <d8827389-1de1-45b6-b572-33c6697f3b13@linaro.org> (raw)
In-Reply-To: <9994b8dd-0522-43ff-94ff-1a94aafd5ce2@linaro.org>
Hi Richard,
On 11/4/24 07:59, Richard Henderson wrote:
> On 11/1/24 01:35, Gustavo Romero wrote:
>> FEAT_CMOW introduces support for controlling cache maintenance
>> instructions executed in EL0/1 and is mandatory from Armv8.8.
>>
>> On real hardware, the main use for this feature is to prevent processes
>> from invalidating or flushing cache lines for addresses they only have
>> read permission, which can impact the performance of other processes.
>>
>> QEMU implements all cache instructions as NOPs, and, according to rule
>> [1], which states that generating any Permission fault when a cache
>> instruction is implemented as a NOP is implementation-defined, no
>> Permission fault is generated for any cache instruction when it lacks
>> read and write permissions.
>>
>> QEMU does not model any cache topology, so the PoU and PoC are before
>> any cache, and rules [2] apply. These rules states that generating any
>> MMU fault for cache instructions in this topology is also
>> implementation-defined. Therefore, for FEAT_CMOW, we do not generate any
>> MMU faults either, instead, we only advertise it in the feature
>> register.
>>
>> [1] Rule R_HGLYG of section D8.14.3, Arm ARM K.a.
>> [2] Rules R_MZTNR and R_DNZYL of section D8.14.3, Arm ARM K.a.
>>
>> Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
>> ---
>> docs/system/arm/emulation.rst | 1 +
>> target/arm/cpu-features.h | 5 +++++
>> target/arm/cpu.h | 1 +
>> target/arm/tcg/cpu64.c | 1 +
>> 4 files changed, 8 insertions(+)
>>
>> diff --git a/docs/system/arm/emulation.rst b/docs/system/arm/emulation.rst
>> index 35f52a54b1..a2a388f091 100644
>> --- a/docs/system/arm/emulation.rst
>> +++ b/docs/system/arm/emulation.rst
>> @@ -26,6 +26,7 @@ the following architecture extensions:
>> - FEAT_BF16 (AArch64 BFloat16 instructions)
>> - FEAT_BTI (Branch Target Identification)
>> - FEAT_CCIDX (Extended cache index)
>> +- FEAT_CMOW (Control for cache maintenance permission)
>> - FEAT_CRC32 (CRC32 instructions)
>> - FEAT_Crypto (Cryptographic Extension)
>> - FEAT_CSV2 (Cache speculation variant 2)
>> diff --git a/target/arm/cpu-features.h b/target/arm/cpu-features.h
>> index 04ce281826..e806f138b8 100644
>> --- a/target/arm/cpu-features.h
>> +++ b/target/arm/cpu-features.h
>> @@ -802,6 +802,11 @@ static inline bool isar_feature_aa64_tidcp1(const ARMISARegisters *id)
>> return FIELD_EX64(id->id_aa64mmfr1, ID_AA64MMFR1, TIDCP1) != 0;
>> }
>> +static inline bool isar_feature_aa64_cmow(const ARMISARegisters *id)
>> +{
>> + return FIELD_EX64(id->id_aa64mmfr1, ID_AA64MMFR1, CMOW) != 0;
>> +}
>
> This isn't used, so it may be omitted.
>
> Otherwise,
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Got it. I wasn’t entirely sure if I should add it for future convenience.
k, I'll omit it if I come across a similar case. Thanks.
Since I'm using it after Peter's comment for v2, I kept it, and added your R-b.
Cheers,
Gustavo
next prev parent reply other threads:[~2024-11-04 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 1:35 [PATCH] target/arm: Enable FEAT_CMOW for -cpu max Gustavo Romero
2024-11-04 10:59 ` Richard Henderson
2024-11-04 14:36 ` Gustavo Romero [this message]
2024-11-04 13:38 ` Peter Maydell
2024-11-04 14:28 ` 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=d8827389-1de1-45b6-b572-33c6697f3b13@linaro.org \
--to=gustavo.romero@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=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).