ppc/pnv: increase kernel size limit to 256MiB
Building kernel with CONFIG_DEBUG_INFO_REDUCED can generate a ~90MB image and building with CONFIG_DEBUG_INFO can generate a ~225M one, both exceeds the current limit of 32MiB. Increasing kernel size limit to 256MiB should fit for now. Signed-off-by: Murilo Opsfelder Araujo <muriloo@linux.ibm.com> Message-Id: <20190225170155.1972-2-muriloo@linux.ibm.com> Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
This commit is contained in:
parent
f6d4dca807
commit
b45b56baee
|
@ -54,6 +54,7 @@
|
|||
#define FW_MAX_SIZE 0x00400000
|
||||
|
||||
#define KERNEL_LOAD_ADDR 0x20000000
|
||||
#define KERNEL_MAX_SIZE (256 * MiB)
|
||||
#define INITRD_LOAD_ADDR 0x60000000
|
||||
|
||||
static const char *pnv_chip_core_typename(const PnvChip *o)
|
||||
|
@ -588,7 +589,7 @@ static void pnv_init(MachineState *machine)
|
|||
long kernel_size;
|
||||
|
||||
kernel_size = load_image_targphys(machine->kernel_filename,
|
||||
KERNEL_LOAD_ADDR, 0x2000000);
|
||||
KERNEL_LOAD_ADDR, KERNEL_MAX_SIZE);
|
||||
if (kernel_size < 0) {
|
||||
error_report("Could not load kernel '%s'",
|
||||
machine->kernel_filename);
|
||||
|
|
Loading…
Reference in a new issue