diff options
| author | Ricardo Perez Blanco <ricardo.perez_blanco@nokia.com> | 2018-12-13 13:47:56 +0000 |
|---|---|---|
| committer | Peter Maydell <peter.maydell@linaro.org> | 2018-12-13 13:47:56 +0000 |
| commit | 751ebc13cca6ca6d68c5112c698aeda27fa389b1 (patch) | |
| tree | e0c0dfd5418140f9fe0d4f78b8f2100cb011a926 /hw/display | |
| parent | bd02b01454c16ca9c07eb7c82588d8b5d0cac9fa (diff) | |
| download | qemu-751ebc13cca6ca6d68c5112c698aeda27fa389b1.zip qemu-751ebc13cca6ca6d68c5112c698aeda27fa389b1.tar.gz qemu-751ebc13cca6ca6d68c5112c698aeda27fa389b1.tar.bz2 | |
Allow AArch64 processors to boot from a kernel placed over 4GB
Architecturally, it's possible for an AArch64 machine to have
all of its RAM over the 4GB mark, but our kernel/initrd loading
code in boot.c assumes that the upper half of the addresses
to load these images to is always zero. Write the whole 64 bit
address into the bootloader code fragment, not just the low half.
Note that, currently, none of the existing QEMU machines have
their main memory over 4GBs, so this was not a user-visible bug.
Signed-off-by: Ricardo Perez Blanco <ricardo.perez_blanco@nokia.com>
[PMM: revised commit message and tweaked some long lines]
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'hw/display')
0 files changed, 0 insertions, 0 deletions