diff options
| author | Gustavo Romero <gustavo.romero@linaro.org> | 2025-10-06 00:10:18 +0000 |
|---|---|---|
| committer | Peter Maydell <peter.maydell@linaro.org> | 2025-10-10 13:22:05 +0100 |
| commit | 00936783abf77ebb47a78312a2e6500c6a13d938 (patch) | |
| tree | f2fe3c15ad081c0e8b018982ebf78657665426c9 /python/qemu/utils/qom.py | |
| parent | 700f08d5829f3736fdfafe92d8223254ffc9c495 (diff) | |
| download | qemu-00936783abf77ebb47a78312a2e6500c6a13d938.zip qemu-00936783abf77ebb47a78312a2e6500c6a13d938.tar.gz qemu-00936783abf77ebb47a78312a2e6500c6a13d938.tar.bz2 | |
target/arm: Enable FEAT_MEC in -cpu max
Advertise FEAT_MEC in AA64MMFR3 ID register for the Arm64 cpu max as a
first step to fully support FEAT_MEC.
The FEAT_MEC is an extension to FEAT_RME that implements multiple
Memory Encryption Contexts (MEC) so the memory in a realm can be
encrypted and accessing it from the wrong encryption context is not
possible. An encryption context allow the selection of a memory
encryption engine.
At this point, no real memory encryption is supported, but software
stacks that rely on FEAT_MEC should work properly.
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
Message-id: 20251006001018.219756-4-gustavo.romero@linaro.org
Message-ID: <20250711140828.1714666-7-gustavo.romero@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'python/qemu/utils/qom.py')
0 files changed, 0 insertions, 0 deletions