Supporting guest private memory in Protected KVM on Android

on YouTube ↗21m

" summary

Port of the proposed guest memory API to pKVM on Arm64 implements guest private memory as a FD-like interface and a kernel-only no-map attribute updated on hypervisor exits so the host never maps pages marked private. It leverages pKVM’s lack of encryption to do in-place sharing (no bounce copies), adds a three-state tracking model and a handshake on unshare where the host must unmap or acknowledge; prototype works for share-only workloads and unshare is exercised only by synthetic tests.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:04Background on PKVM
3. 3:13Guest memory challenges
4. 6:04Key differences in PKVM
5. 8:16Use case for DRM
6. 11:28Problem statement
7. 12:31State tracking solution
8. 14:57Transition protocols
9. 17:25Mapping and validation
10. 19:14Testing and future work
11. 20:15Q&A

" related talks

• 22mPreserving guest memory across kexecJames Gowans · Linux Plumbers Conference 2022
• 38mPanel Discussion: KVM-based Virtualization Contributor Q&AWill Deacon, Paolo Bonzini, Sean Christopherson, Christoffer Dall, Kashyap Chamarthy, Susie Li · KVM Forum 2022
• 11mAdvanced Parallel Memory VirtualizationYulei Zhang · KVM Forum 2020
• 38mKernel Hardening: Protecting the Protection MechanismsIgor Stoppa · Linux Security Summit Europe 2018
• 50mPanel Discussion: KVM-based Virtualization Contributor Q&AHubertus Franke, Stefan Hajnoczi, Richard W.M. Jones, Susie Li, David Kaplan, Peter Maydell · KVM Forum 2020
• 37mHardware Error Handling Improvement for Reliable KVM HypervisorMitsuhiro Tanino · Collaboration Summit 2013
• 34mA New Proposal for Protecting Kernel Data MemoryIgor Stoppa · Linux Security Summit Europe 2019
• 26mCooperative DMA in a memory-oversubscribed environmentJames Gowans · Linux Plumbers Conference 2022