aboutsummaryrefslogtreecommitdiff
path: root/scripts/dump-guest-memory.py
diff options
context:
space:
mode:
authorPeter Maydell <peter.maydell@linaro.org>2018-03-13 15:34:51 +0000
committerPeter Maydell <peter.maydell@linaro.org>2018-03-19 18:23:24 +0000
commit43118f4351c1c430aa5c32aed80dcfe0b525a1f0 (patch)
tree9e0b42fab21de07b66e6934850436f7462b3ddd6 /scripts/dump-guest-memory.py
parent01e02f5aa74315f81b62872a50fe1b3e96dd00df (diff)
downloadqemu-43118f4351c1c430aa5c32aed80dcfe0b525a1f0.zip
qemu-43118f4351c1c430aa5c32aed80dcfe0b525a1f0.tar.gz
qemu-43118f4351c1c430aa5c32aed80dcfe0b525a1f0.tar.bz2
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 'scripts/dump-guest-memory.py')
0 files changed, 0 insertions, 0 deletions