diff options
| author | Oliver Upton <[email protected]> | 2025-03-05 23:08:23 +0000 |
|---|---|---|
| committer | Oliver Upton <[email protected]> | 2025-03-06 00:55:41 +0000 |
| commit | 9d91227364330fd1735d6fc3f7226f854f9f7b8c (patch) | |
| tree | 660e490e1cadab9a88e736111ac54feea2f6ebeb /net/unix/unix_bpf.c | |
| parent | KVM: selftests: arm64: Test writes to MIDR,REVIDR,AIDR (diff) | |
| download | kernel-9d91227364330fd1735d6fc3f7226f854f9f7b8c.tar.gz kernel-9d91227364330fd1735d6fc3f7226f854f9f7b8c.zip | |
KVM: arm64: Copy guest CTR_EL0 into hyp VM
Since commit 2843cae26644 ("KVM: arm64: Treat CTR_EL0 as a VM feature
ID register") KVM has allowed userspace to configure the VM-wide view of
CTR_EL0, falling back to trap-n-emulate if the value doesn't match
hardware. It appears that this has worked by chance in protected-mode
for some time, and on systems with FEAT_EVT protected-mode
unconditionally sets TID4 (i.e. TID2 traps sans CTR_EL0).
Forward the guest CTR_EL0 value through to the hyp VM and align the
TID2/TID4 configuration with the non-protected setup.
Fixes: 2843cae26644 ("KVM: arm64: Treat CTR_EL0 as a VM feature ID register")
Reviewed-by: Marc Zyngier <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Oliver Upton <[email protected]>
Diffstat (limited to 'net/unix/unix_bpf.c')
0 files changed, 0 insertions, 0 deletions