[PATCH v15 00/11] KVM//x86/arm/arm64: dirty page logging for ARMv7/8 (3.18.0-rc2)
Mario Smarduch
m.smarduch at samsung.com
Sun Dec 14 23:27:57 PST 2014
Patch series adds support for armv7/8 dirty page logging. Also we move
towards generic dirty page logging interface and move some common code to
generic layer currently shared by x86, armv7 and armv8.
armv7/8 Dirty page logging implementation overivew-
- initially write protects memory region 2nd stage page tables
- read dirty page log and again write protect dirty pages for next pass.
- second stage huge page are dissolved into pages to keep track of
dirty memory at page granularity. Tracking at huge page granularity limits
migration to an almost idle system. Small page size logging supports higher
memory dirty rates. armv7 supports only 2MB Huge pages, armv8 may support
2MB with kernel configurered to 4k page and 512MB for 64k page. Additional
logic has been included to support PUD sized 2nd stage 1GB huge pages which
apply to 4k page, 48 bit address space. Host kernel and ARM KVM support 2MB
and 512MB huge pages.
- In the event migration is canceled, normal behavior is resumed huge pages
are rebuilt over time.
Testing:
- ARMv7:
o Fast Models Live Migration and shared memory mmio described below.
For both instances correctness is validated through checksum of source and
destination file copies on both ends. Precise tests with instructions
will appear shortly at:
https://github.com/mjsmar/arm-dirtylog-tests
o To test migration Christoffer's patches need to be applied
https://lists.cs.columbia.edu/pipermail/kvmarm/2014-December/012809.html
"Fix vgic initialization problems". You can try validate without the patches
(through checksums) but destination VM will not be responsive
o Tested with 2MB huge pages, 4k pages
- ARMv8:
o Currently migration is not supported on ARMv8 another method is used to
validate dirty page logging. Used Foundation Model 9.0.xx for testing.
Again details will appear at:
https://github.com/mjsmar/arm-dirtylog-tests
o Test Description:
- Added mmio device to QEMU 'virt' with on board memory (8MB in this case),
Device memory is Posix shared memory segment visible to host.
Enabled dirty logging for that memslot.
- Added memslot migration thread to export dirty bit map to host.
- Implemented memory migration thread on host.
o Operation:
- On Guest application mmaps() the region and writes to it
- The host migration thread does a pre-copy of /dev/shm/aeshmem to a host
file, repeatedly requests QEMU for memory region dirty page log,
incrementally copies dirty pages from /dev/shm/aeshmem to host file.
- Guest application is stopped and both /dev/shm/aeshmem and host file are
checksummed and check for match to validate dirty page log applied
incremental updates, validating dirty page logging.
- Tested with 2MB huge pages, 64k pages.
- 512MB not tested yet due to hardware limitations.
- 1GB not tested will require customized setup and hardcoding in kernel.
o To test modifed QEMU is needed to map VM GICC at same offset as Foundation
Models gic-v3 GICV (thanks to Marc's insight), currently QEMU hardcodes
GICC to 64KB aligned page.
Changes since v14:
- Fixed a bug referencsing 2nd stage pmd pfn instead IPA to flush 2nd stage TLB.
- Fixed initial write protect to include KVM_MR_MOVE case.
- Fixed timing issue between tlb flush and completion on other CPUs.
- Added PUD write protect and clear.
- Refactored some code in kvm/mmu.c due to 3rd issue above.
- Combined armv7 and 8 patches into one series
- Reworded descirption for kvm_vm_ioctl_get_dirty_log(), applied Paolos changes
- rebased to 3.18.0-rc2
Changes since v13:
- Addressed comments from Cornelia, Paolo, Marc, and Christoffer
- Most signifcant change is reduce number of arguments to stage2_set_pte
- Another is introduce Kconfig symbol for generic kvm_get_dirty_log_protect()
Changes since v12:
- Added Paolos and James Hogan's comments to extend kvm_get_dirty_log() to
make it further generic by adding write protection in addition to dirty bit
map handling. This led to new generic function kvm_get_dirty_log_protect().
Changes since v11:
- Implemented Alex's comments to simplify generic layer.
Changes since v10:
- addressed wanghaibin comments
- addressed Christoffers comments
Changes since v9:
- Split patches into generic and architecture specific variants for TLB Flushing
and dirty log read (patches 1,2 & 3,4,5,6)
- rebased to 3.16.0-rc1
- Applied Christoffers comments
Mario Smarduch (10):
KVM: Add architecture-defined TLB flush support
KVM: Add generic support for dirty page logging
KVM: arm: Add ARMv7 API to flush TLBs
KVM: arm: Add initial dirty page locking support
KVM: arm: dirty logging write protect support
KVM: arm: page logging 2nd stage fault handling
KVM: arm64: ARMv8 header changes for page logging
KVM: arm64: Add HYP nterface to flush 1st/2nd stage
KVM: arm/arm64: Enable Dirty Page logging for ARMv8
KVM: arm/arm64: Add support to dissolve huge PUD
Paolo Bonzini (1):
KVM: x86: switch to kvm_get_dirty_log_protect
arch/arm/include/asm/kvm_asm.h | 1 +
arch/arm/include/asm/kvm_host.h | 2 +
arch/arm/include/asm/kvm_mmu.h | 29 ++++
arch/arm/include/asm/pgtable-3level.h | 1 +
arch/arm/kvm/Kconfig | 2 +
arch/arm/kvm/arm.c | 32 +++-
arch/arm/kvm/interrupts.S | 11 ++
arch/arm/kvm/mmu.c | 304 ++++++++++++++++++++++++++++++++-
arch/arm64/include/asm/kvm_asm.h | 1 +
arch/arm64/include/asm/kvm_host.h | 1 +
arch/arm64/include/asm/kvm_mmu.h | 30 ++++
arch/arm64/include/asm/pgtable-hwdef.h | 4 +
arch/arm64/kvm/Kconfig | 2 +
arch/arm64/kvm/hyp.S | 22 +++
arch/x86/include/asm/kvm_host.h | 3 -
arch/x86/kvm/Kconfig | 1 +
arch/x86/kvm/mmu.c | 4 +-
arch/x86/kvm/x86.c | 72 ++------
include/linux/kvm_host.h | 9 +
virt/kvm/Kconfig | 9 +
virt/kvm/kvm_main.c | 82 +++++++++
21 files changed, 549 insertions(+), 73 deletions(-)
--
1.9.1
More information about the linux-arm-kernel
mailing list