summaryrefslogtreecommitdiff
path: root/kvm.h
diff options
context:
space:
mode:
authorJan Kiszka <jan.kiszka@web.de>2009-04-26 18:03:40 +0200
committerAnthony Liguori <aliguori@us.ibm.com>2009-05-01 10:11:02 -0500
commit57ba0792ca430557ec89aa3daeceb42034161706 (patch)
treeada30ecaa40ef35e868dd3efec77cd3a061aa9c5 /kvm.h
parenta2daabc49a94098b12b499b8b82c48abb0b7a66a (diff)
downloadqemu-57ba0792ca430557ec89aa3daeceb42034161706.tar.gz
kvm: Avoid COW if KVM MMU is asynchronous
Avi Kivity wrote: > Suggest wrapping in a function and hiding it deep inside kvm-all.c. > Done in v2: ----------> If the KVM MMU is asynchronous (kernel does not support MMU_NOTIFIER), we have to avoid COW for the guest memory. Otherwise we risk serious breakage when guest pages change there physical locations due to COW after fork. Seen when forking smbd during runtime via -smb. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'kvm.h')
-rw-r--r--kvm.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/kvm.h b/kvm.h
index efce1450d5..5a52f51cb9 100644
--- a/kvm.h
+++ b/kvm.h
@@ -46,6 +46,8 @@ int kvm_log_stop(target_phys_addr_t phys_addr, target_phys_addr_t len);
int kvm_has_sync_mmu(void);
+void kvm_setup_guest_memory(void *start, size_t size);
+
int kvm_coalesce_mmio_region(target_phys_addr_t start, ram_addr_t size);
int kvm_uncoalesce_mmio_region(target_phys_addr_t start, ram_addr_t size);