diff options
| author | Philippe Mathieu-Daudé <f4bug@amsat.org> | 2020-06-01 16:29:23 +0200 |
|---|---|---|
| committer | Laurent Vivier <laurent@vivier.eu> | 2020-06-09 19:58:53 +0200 |
| commit | 7df9f0283905c25d9c317f782cde9f52bb1916ce (patch) | |
| tree | ca66f84b4fab738a8902e6bc6ebbd713a8589b03 /scsi/utils.c | |
| parent | 547f8f6452579506fbde2f0a1aa5fc0469dc45a3 (diff) | |
| download | qemu-7df9f0283905c25d9c317f782cde9f52bb1916ce.zip qemu-7df9f0283905c25d9c317f782cde9f52bb1916ce.tar.gz qemu-7df9f0283905c25d9c317f782cde9f52bb1916ce.tar.bz2 | |
hw/arm/aspeed: Correct DRAM container region size
memory_region_set_size() handle the 16 Exabytes limit by
special-casing the UINT64_MAX value. This is not a problem
for the 32-bit maximum, 4 GiB.
By using the UINT32_MAX value, the aspeed-ram-container
MemoryRegion ends up missing 1 byte:
$ qemu-system-arm -M ast2600-evb -S -monitor stdio
(qemu) info mtree
address-space: aspeed.fmc-ast2600-dma-dram
0000000080000000-000000017ffffffe (prio 0, i/o): aspeed-ram-container
0000000080000000-00000000bfffffff (prio 0, ram): ram
00000000c0000000-ffffffffffffffff (prio 0, i/o): max_ram
Fix by using the correct value. We now have:
address-space: aspeed.fmc-ast2600-dma-dram
0000000080000000-000000017fffffff (prio 0, i/o): aspeed-ram-container
0000000080000000-00000000bfffffff (prio 0, ram): ram
00000000c0000000-ffffffffffffffff (prio 0, i/o): max_ram
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20200601142930.29408-2-f4bug@amsat.org>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
Diffstat (limited to 'scsi/utils.c')
0 files changed, 0 insertions, 0 deletions