aboutsummaryrefslogtreecommitdiff
path: root/util/osdep.c
diff options
context:
space:
mode:
authorDavid Hildenbrand <david@redhat.com>2018-06-07 17:47:04 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2018-06-28 19:05:31 +0200
commit4d8938a05db15dea2c86c4ab9c5f872f160d2188 (patch)
tree51ae26035da86e61cf247f471e63b3b234fb8fa1 /util/osdep.c
parent93d1499c8119989e3eb9a6936c5a18aaaaca6330 (diff)
downloadqemu-4d8938a05db15dea2c86c4ab9c5f872f160d2188.zip
qemu-4d8938a05db15dea2c86c4ab9c5f872f160d2188.tar.gz
qemu-4d8938a05db15dea2c86c4ab9c5f872f160d2188.tar.bz2
memory-device: turn alignment assert into check
The start of the address space indicates which maximum alignment is supported by our machine (e.g. ppc, x86 1GB). This is helpful to catch fragmenting guest physical memory in strange fashions. Right now we can crash QEMU by e.g. (there might be easier examples) qemu-system-x86_64 -m 256M,maxmem=20G,slots=2 \ -object memory-backend-file,id=mem0,size=8192M,mem-path=/dev/zero,align=8192M \ -device pc-dimm,id=dimm1,memdev=mem0 Signed-off-by: David Hildenbrand <david@redhat.com> Message-Id: <20180607154705.6316-2-david@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Reviewed-by: Igor Mammedov <imammedo@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'util/osdep.c')
0 files changed, 0 insertions, 0 deletions