diff options
| author | Peter Maydell | 2019-05-16 16:47:30 +0200 |
|---|---|---|
| committer | Peter Maydell | 2019-06-17 16:11:18 +0200 |
| commit | e70af24b42190481e19c9adb727b97a0fc794ea8 (patch) | |
| tree | f35ba34febd81b3172bf6e54f7c28e4207c90fab /include/exec/user | |
| parent | Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (diff) | |
| download | qemu-e70af24b42190481e19c9adb727b97a0fc794ea8.tar.gz qemu-e70af24b42190481e19c9adb727b97a0fc794ea8.tar.xz qemu-e70af24b42190481e19c9adb727b97a0fc794ea8.zip | |
hw/arm/boot: Don't assume RAM starts at address zero
In the Arm kernel/initrd loading code, in some places we make the
incorrect assumption that info->ram_size can be treated as the
address of the end of RAM, as for instance when we calculate the
available space for the initrd using "info->ram_size - info->initrd_start".
This is wrong, because many Arm boards (including "virt") specify
a non-zero info->loader_start to indicate that their RAM area
starts at a non-zero physical address.
Correct the places which make this incorrect assumption.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Tested-by: Mark Rutland <mark.rutland@arm.com>
Message-id: 20190516144733.32399-2-peter.maydell@linaro.org
Diffstat (limited to 'include/exec/user')
0 files changed, 0 insertions, 0 deletions