KVM: arm64: nv: A couple more VNCR fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCRarch/ | +25 | 0 replies | |
| 2/2 | KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFNarch/ arch/ arch/ | +14 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] KVM: arm64: nv: A couple more VNCR fixes
Another day, another handful of ugly MMU bugs.
The first addresses an issue where the host stage-1 VNCR mapping only relies on the guest stage-1 permissions, potentially allowing RW accesses to an RO PFN.
The second avoids a BUG_ON() in the case that the output of stage-1 translation exists outside of a memslot, and instead does the usual thing and injects an SEA.
Based on kvmarm/next since the first pile of MMU changes was taken (thanks!)
Oliver Upton (2):
KVM: arm64: nv: Respect read-only PFN when mapping L1 VNCR
KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN
arch/arm64/include/asm/kvm_nested.h | 8 ++++++ arch/arm64/kvm/at.c | 8 ------ arch/arm64/kvm/nested.c | 40 +++++++++++++++++++++-------- 3 files changed, 38 insertions(+), 18 deletions(-)
base-commit: 406f0c31f47877db036e885f15830106b89ca950
Signature · 1 line
2.47.3