Hi Paolo,
A week ago, I was hoping being done with the 5.10 fixes. I should
obviously know better.
Thanks to Yanan's excellent work, we have another set of page table
fixes, all plugging issues introduced with our new page table code.
The problems range from memory leak to TLB conflicts, all of which are
serious enough to be squashed right away.
Are we done yet? Fingers crossed.
Please pull,
M.
The following changes since commit 23bde34771f1ea92fb5e6682c0d8c04304d34b3b:
KVM: arm64: vgic-v3: Drop the reporting of GICR_TYPER.Last for userspace (2020-11-17 18:51:09 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-5.10-5
for you to fetch changes up to 7d894834a305568a0168c55d4729216f5f8cb4e6:
KVM: arm64: Add usage of stage 2 fault lookup level in user_mem_abort() (2020-12-02 09:53:29 +0000)
----------------------------------------------------------------
kvm/arm64 fixes for 5.10, take #5
- Don't leak page tables on PTE update
- Correctly invalidate TLBs on table to block transition
- Only update permissions if the fault level matches the
expected mapping size
----------------------------------------------------------------
Yanan Wang (3):
KVM: arm64: Fix memory leak on stage2 update of a valid PTE
KVM: arm64: Fix handling of merging tables into a block entry
KVM: arm64: Add usage of stage 2 fault lookup level in user_mem_abort()
arch/arm64/include/asm/esr.h | 1 +
arch/arm64/include/asm/kvm_emulate.h | 5 +++++
arch/arm64/kvm/hyp/pgtable.c | 17 ++++++++++++++++-
arch/arm64/kvm/mmu.c | 11 +++++++++--
4 files changed, 31 insertions(+), 3 deletions(-)
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
