aboutsummaryrefslogtreecommitdiff
path: root/python
diff options
context:
space:
mode:
authorPeter Xu <peterx@redhat.com>2021-05-17 04:23:50 -0400
committerPaolo Bonzini <pbonzini@redhat.com>2021-05-26 14:49:46 +0200
commitb4420f198dd8eab53cf6062c1871d0e5f5601e86 (patch)
treeff96a5909b465cc9edec20e9ac27e14d4ab9d3e6 /python
parenta81a592698c5cf3d84486b00c84b7979dfa0a3da (diff)
downloadqemu-b4420f198dd8eab53cf6062c1871d0e5f5601e86.zip
qemu-b4420f198dd8eab53cf6062c1871d0e5f5601e86.tar.gz
qemu-b4420f198dd8eab53cf6062c1871d0e5f5601e86.tar.bz2
KVM: Dirty ring support
KVM dirty ring is a new interface to pass over dirty bits from kernel to the userspace. Instead of using a bitmap for each memory region, the dirty ring contains an array of dirtied GPAs to fetch (in the form of offset in slots). For each vcpu there will be one dirty ring that binds to it. kvm_dirty_ring_reap() is the major function to collect dirty rings. It can be called either by a standalone reaper thread that runs in the background, collecting dirty pages for the whole VM. It can also be called directly by any thread that has BQL taken. Signed-off-by: Peter Xu <peterx@redhat.com> Message-Id: <20210506160549.130416-11-peterx@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions