diff options
| author | Li Zhijian | 2019-01-17 13:49:04 +0100 |
|---|---|---|
| committer | Paolo Bonzini | 2019-02-05 16:50:18 +0100 |
| commit | aab50e53440b2fe432a5a59cbd0e7ec241a1169b (patch) | |
| tree | 14f1adec7cd8f7dd2a7b303e0a1686e1f86ad2d5 /target/i386/hvf/x86_decode.c | |
| parent | i386: import & use bootparam.h (diff) | |
| download | qemu-aab50e53440b2fe432a5a59cbd0e7ec241a1169b.tar.gz qemu-aab50e53440b2fe432a5a59cbd0e7ec241a1169b.tar.xz qemu-aab50e53440b2fe432a5a59cbd0e7ec241a1169b.zip | |
i386: allow to load initrd below 4 GB for recent linux
Since linux commit: cf8fa920cb42 ("i386: handle an initrd in highmem (version 2)")
linux has supported initrd up to 4 GB, but the header field
ramdisk_max is still set to 2 GB to avoid "possible bootloader bugs".
When use '-kernel vmlinux -initrd initrd.cgz' to launch a VM,
the firmware(it could be linuxboot_dma.bin) helps to read initrd
contents into guest memory(below ramdisk_max) and jump to kernel.
that's similar with what bootloader does, like grub.
In addition, initrd_max is uint32_t simply because QEMU doesn't support
the 64-bit boot protocol (specifically the ext_ramdisk_image field).
Therefore here just limit initrd_max to UINT32_MAX simply as well to
allow initrd to be loaded below 4 GB.
NOTE: it's possible that linux protocol within [0x208, 0x20c]
supports up to 4 GB initrd as well.
CC: Paolo Bonzini <pbonzini@redhat.com>
CC: Richard Henderson <rth@twiddle.net>
CC: Eduardo Habkost <ehabkost@redhat.com>
CC: "Michael S. Tsirkin" <mst@redhat.com>
CC: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'target/i386/hvf/x86_decode.c')
0 files changed, 0 insertions, 0 deletions