diff options
author | David Hildenbrand <david@redhat.com> | 2020-10-08 10:30:27 +0200 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2020-11-03 07:19:26 -0500 |
commit | 780a4d24e73dd0a7c7fc3f6f8b104aab70b7bfff (patch) | |
tree | 7fc9378dfe460cfa29fc400eaa3c429f5fe98ade | |
parent | 228957fea3a998735524abf6354634f1fb710e61 (diff) | |
download | qemu-780a4d24e73dd0a7c7fc3f6f8b104aab70b7bfff.zip qemu-780a4d24e73dd0a7c7fc3f6f8b104aab70b7bfff.tar.gz qemu-780a4d24e73dd0a7c7fc3f6f8b104aab70b7bfff.tar.bz2 |
memory-device: Support big alignment requirements
Let's warn instead of bailing out - the worst thing that can happen is
that we'll fail hot/coldplug later. The user got warned, and this should
be rare.
This will be necessary for memory devices with rather big (user-defined)
alignment requirements - say a virtio-mem device with a 2G block size -
which will become important, for example, when supporting vfio in the
future.
Reviewed-by: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Wei Yang <richardw.yang@linux.intel.com>
Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>
Cc: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20201008083029.9504-5-david@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
-rw-r--r-- | hw/mem/memory-device.c | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c index 4bc9cf0..8a736f1 100644 --- a/hw/mem/memory-device.c +++ b/hw/mem/memory-device.c @@ -119,9 +119,10 @@ static uint64_t memory_device_get_free_addr(MachineState *ms, /* start of address space indicates the maximum alignment we expect */ if (!QEMU_IS_ALIGNED(range_lob(&as), align)) { - error_setg(errp, "the alignment (0x%" PRIx64 ") is not supported", - align); - return 0; + warn_report("the alignment (0x%" PRIx64 ") exceeds the expected" + " maximum alignment, memory will get fragmented and not" + " all 'maxmem' might be usable for memory devices.", + align); } memory_device_check_addable(ms, size, &err); @@ -151,7 +152,7 @@ static uint64_t memory_device_get_free_addr(MachineState *ms, return 0; } } else { - if (range_init(&new, range_lob(&as), size)) { + if (range_init(&new, QEMU_ALIGN_UP(range_lob(&as), align), size)) { error_setg(errp, "can't add memory device, device too big"); return 0; } |