summaryrefslogtreecommitdiff
path: root/exec.c
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 09:44:11 -0500
commit6f0437e8de95aebbd9e66af4d074c0d5119d86b7 (patch)
treed761a5e3bf4b2c4075415c3f880e65baf33856d8 /exec.c
parent8563d5b31d1b1b43f3304ba59535b6b878c15a2d (diff)
downloadqemu-6f0437e8de95aebbd9e66af4d074c0d5119d86b7.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 'exec.c')
-rw-r--r--exec.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/exec.c b/exec.c
index 2effd04f62..c64938124b 100644
--- a/exec.c
+++ b/exec.c
@@ -2484,6 +2484,9 @@ ram_addr_t qemu_ram_alloc(ram_addr_t size)
last_ram_offset += size;
+ if (kvm_enabled())
+ kvm_setup_guest_memory(new_block->host, size);
+
return new_block->offset;
}