[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RESOLVED] aarch64 edk2 + linux kernel crash with gicv4
From: |
Peter Maydell |
Subject: |
Re: [RESOLVED] aarch64 edk2 + linux kernel crash with gicv4 |
Date: |
Wed, 22 Jun 2022 10:15:15 +0100 |
On Wed, 22 Jun 2022 at 06:07, Alex Bennée <alex.bennee@linaro.org> wrote:
> Richard Henderson <richard.henderson@linaro.org> writes:
> > The symptom is an early-ish crash booting the linux kernel -- without
> > earlycon there is no output at all. Reproducing it requires both
> > -bios QEMU_EFI.fd and -kernel Image.gz. Using only one of the two
> > options works.
>
> What should the combination of the two options mean? Usually the
> firmware loads the kernel and -kernel is a shortcut hack to avoid the
> firmware setup. If you specify both does the firmware still run but
> somehow find the kernel mapped in memory?
It's like x86 -- it means "load the BIOS image, and provide the
kernel/initrd via the fw_cfg device, so that a QEMU-aware BIOS
can read the supplied kernel/initrd from fw_cfg and boot them".
thanks
-- PMM