diff options
| author | Peter Maydell | 2018-03-13 16:34:51 +0100 |
|---|---|---|
| committer | Peter Maydell | 2018-03-19 19:23:24 +0100 |
| commit | 43118f4351c1c430aa5c32aed80dcfe0b525a1f0 (patch) | |
| tree | 9e0b42fab21de07b66e6934850436f7462b3ddd6 /include/exec/memory.h | |
| parent | hw/arm/raspi: Don't do board-setup or secure-boot for raspi3 (diff) | |
| download | qemu-43118f4351c1c430aa5c32aed80dcfe0b525a1f0.tar.gz qemu-43118f4351c1c430aa5c32aed80dcfe0b525a1f0.tar.xz qemu-43118f4351c1c430aa5c32aed80dcfe0b525a1f0.zip | |
hw/arm/boot: assert that secure_boot and secure_board_setup are false for AArch64
Add some assertions that if we're about to boot an AArch64 kernel,
the board code has not mistakenly set either secure_boot or
secure_board_setup. It doesn't make sense to set secure_boot,
because all AArch64 kernels must be booted in non-secure mode.
It might in theory make sense to set secure_board_setup, but
we don't currently support that, because only the AArch32
bootloader[] code calls this hook; bootloader_aarch64[] does not.
Since we don't have a current need for this functionality, just
assert that we don't try to use it. If it's needed we'll add
it later.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-id: 20180313153458.26822-3-peter.maydell@linaro.org
Diffstat (limited to 'include/exec/memory.h')
0 files changed, 0 insertions, 0 deletions
