-
Christian Borntraeger authored
By default qemu will use MAP_PRIVATE for guest pages. This will write protect pages and thus break on s390 systems that dont support this feature. Therefore qemu has a hack to always use MAP_SHARED for s390. But MAP_SHARED has other problems (no dirty pages tracking, a lot more swap overhead etc.) Newer systems allow the distinction via KVM_CAP_S390_COW. With this feature qemu can use the standard qemu alloc if available, otherwise it will use the old s390 hack. Signed-off-by:
Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by:
Jens Freimann <jfrei@linux.vnet.ibm.com>
Acked-by:
Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by:
Alexander Graf <agraf@suse.de>Christian Borntraeger authoredBy default qemu will use MAP_PRIVATE for guest pages. This will write protect pages and thus break on s390 systems that dont support this feature. Therefore qemu has a hack to always use MAP_SHARED for s390. But MAP_SHARED has other problems (no dirty pages tracking, a lot more swap overhead etc.) Newer systems allow the distinction via KVM_CAP_S390_COW. With this feature qemu can use the standard qemu alloc if available, otherwise it will use the old s390 hack. Signed-off-by:
Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by:
Jens Freimann <jfrei@linux.vnet.ibm.com>
Acked-by:
Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by:
Alexander Graf <agraf@suse.de>
Loading