David Hildenbrand 4d8938a05d 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>

2018-06-28 19:05:31 +02:00

..

Makefile.objs

pc-dimm: factor out MemoryDevice interface

2018-05-07 10:00:02 -03:00

memory-device.c

memory-device: turn alignment assert into check

2018-06-28 19:05:31 +02:00

nvdimm.c

nvdimm: fix typo in label-size definition

2018-05-23 17:02:03 +03:00

pc-dimm.c

pc-dimm: fix error messages if no slots were defined

2018-05-11 14:33:40 +02:00

trace-events

docs: fix broken paths to docs/devel/tracing.txt

2017-07-31 13:12:53 +03:00