KVM: arm64: FEAT_{S1POE,ATS1A} support fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | KVM: arm64: Key CPTR_EL2.E0POE propagation on FEAT_S1POEarch/ | +1 | 0 replies | |
| 2/3 | KVM: arm64: Wire AT S1E1A in the system instruction handling tablearch/ | +1 | 0 replies | |
| 3/3 | arm64: cpufeature: Expose ID_AA64ISAR2_EL1.ATS1A to KVMarch/ | +1 | 0 replies |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Oliver Upton | Joey Gouly |
|---|---|---|
| Series | R-b | R-b |
| 1/3 | ||
| 2/3 | ||
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] KVM: arm64: FEAT_{S1POE,ATS1A} support fixes
Whilst working on a slightly unrelated feature (FEAT_NV3), I found out that an L2 guest wouldn't boot if the host was exposed to FEAT_S1POE.
Upon investigation (and hours wasted in a SW model), it became apparent that while the AT S1E1A code was ready for action, it had never been fully plugged in (blame the usual suspect...).
This resulted in an extremely odd failure mode, with an L2 being unable to make forward progress, but KVM at L1 not taking the hint that something was really wrong. Additionally, an embarrassing typo was spotted in the CPTR_EL2 handling.
With this in, FEAT_S1POE no longer breaks our NV guests.
Marc Zyngier (3):
KVM: arm64: Key CPTR_EL2.E0POE propagation on FEAT_S1POE
KVM: arm64: Wire AT S1E1A in the system instruction handling table
arm64: cpufeature: Expose ID_AA64ISAR2_EL1.ATS1A to KVM
arch/arm64/kernel/cpufeature.c | 1 + arch/arm64/kvm/hyp/include/hyp/switch.h | 2 +- arch/arm64/kvm/sys_regs.c | 1 + 3 files changed, 3 insertions(+), 1 deletion(-)
Signature · 1 line
2.47.3