Fixes for running U-boot under QEMU/KVM
v2 cover Fixes for running U-boot under QEMU/KVM
This series fixes a number of issues that exist in the QEMU/mach-virt port of u-boot, and that prevent it from executing correctly under virtualization (as opposed to TCG emulation)
As the Linux EFI subsystem maintainer, I am looking to increase test coverage for the EFI related changes that are under development for Linux, and one of the things I plan to do is start using U-boot as test firmware for boot testing. This can be done under TCG emulation, but given how loosely TCG implements the architecture, it is better to test under virtualization as well.
With these changes applied, u-boot can boot Linux in EFI mode under KVM.
Changes since v1:
- fix LPAE memory type for DCACHE_WRITETHROUGH as well, and add some comments to clarify what the values are based on (patch #1)
- only override the flash accessors that we need to (patch #5)
- add Heinrich's ack to #2 and #4
Ard Biesheuvel (5):
arm: enable allocate-on-read for LPAE's DCACHE_WRITEBACK/_WRITETHROUGH
arm: qemu: enable LPAE on 32-bit
arm: qemu: implement enable_caches()
arm: qemu: disable the EFI workaround for older GRUB
arm: qemu: override flash accessors to use virtualizable instructions
arch/arm/include/asm/system.h | 23 +++++++++--- board/emulation/qemu-arm/qemu-arm.c | 37 ++++++++++++++++++++ configs/qemu_arm_defconfig | 2 ++ include/configs/qemu-arm.h | 1 + 4 files changed, 59 insertions(+), 4 deletions(-)
Signature · 1 line
2.26.2
PATCH v2 1/5 arm: enable allocate-on-read for LPAE's DCACHE_WRITEBACK/_WRITETHROUGH
The LPAE versions of DCACHE_WRITEBACK and DCACHE_WRITETHROUGH are currently defined as no-allocate for both reads and writes, which deviates from the non-LPAE definition, and mostly defeats the purpose of enabling the caches in the first place.
So align LPAE with !LPAE, and enable allocate-on-read for both. And while at it, add some clarification about the meaning of the chosen values.
--- arch/arm/include/asm/system.h | 23 ++++++++++++++++---- 1 file changed, 19 insertions(+), 4 deletions(-)
arch/arm/include/asm/system.h +19 -4
@@ -442,10 +442,16 @@ static inline void set_dacr(unsigned int val)#define TTBCR_EPD0 (0 << 7)/* -* Memory types +* VMSAv8-32 Long-descriptor format memory region attributes +* (ARM Architecture Reference Manual section G5.7.4 [DDI0487E.a]) +* +* MAIR0[ 7: 0] 0x00 Device-nGnRnE (aka Strongly-Ordered) +* MAIR0[15: 8] 0xaa Outer/Inner Write-Through, Read-Allocate No Write-Allocate +* MAIR0[23:16] 0xee Outer/Inner Write-Back, Read-Allocate No Write-Allocate +* MAIR0[31:24] 0xff Outer/Inner Write-Back, Read-Allocate Write-Allocate */ -#define MEMORY_ATTRIBUTES ((0x00 << (0 * 8)) | (0x88 << (1 * 8)) | \ - (0xcc << (2 * 8)) | (0xff << (3 * 8))) +#define MEMORY_ATTRIBUTES ((0x00 << (0 * 8)) | (0xaa << (1 * 8)) | \ + (0xee << (2 * 8)) | (0xff << (3 * 8)))/* options available for data cache on each page */ enum dcache_option {
@@ -468,7 +474,16 @@ enum dcache_option {#define TTB_SECT_B_MASK (1 << 2)#define TTB_SECT (2 << 0) -/* options available for data cache on each page */ +/* +* Short-descriptor format memory region attributes, without TEX remap +* (ARM Architecture Reference Manual section G5.7.2 [DDI0487E.a]) +* +* TEX[0] C B +* 0 0 0 Device-nGnRnE (aka Strongly-Ordered) +* 0 1 0 Outer/Inner Write-Through, Read-Allocate No Write-Allocate +* 0 1 1 Outer/Inner Write-Back, Read-Allocate No Write-Allocate +* 1 1 1 Outer/Inner Write-Back, Read-Allocate Write-Allocate +*/ enum dcache_option {DCACHE_OFF =TTB_SECT_DOMAIN (0 ) |TTB_SECT_XN_MASK |TTB_SECT ,DCACHE_WRITETHROUGH =DCACHE_OFF |TTB_SECT_C_MASK ,
Signature · 1 line
2.26.2
PATCH v2 2/5 arm: qemu: enable LPAE on 32-bit
In reply to Ard BiesheuvelQEMU's mach-virt machine only supports selecting CPU models that implement the virtualization extensions, and are therefore guaranteed to support LPAE as well.
Initially, QEMU would not allow emulating these CPUs running in HYP mode (or EL2, for AArch64), but today, it also contains a complete implementation of the virtualization extensions themselves.
This means we could be running U-Boot in HYP mode, in which case the LPAE long descriptor page table format is the only format that is supported. If we are not running in HYP mode, we can use either.
So let's enable CONFIG_ARMV7_LPAE for qemu_arm_defconfig so that we get the best support for running with the MMU and caches enabled at any privilege level.
--- configs/qemu_arm_defconfig | 1 + 1 file changed, 1 insertion(+)
configs/qemu_arm_defconfig +1 -0
@@ -1,5 +1,6 @@ CONFIG_ARM=y CONFIG_ARM_SMCCC=y +CONFIG_ARMV7_LPAE=y CONFIG_ARCH_QEMU=y CONFIG_ENV_SIZE=0x40000 CONFIG_ENV_SECT_SIZE=0x40000
Signature · 1 line
2.26.2
PATCH v2 3/5 arm: qemu: implement enable_caches()
In reply to Ard BiesheuvelAdd an override for enable_caches to enable the I and D caches, along with the cached 1:1 mapping of all of DRAM. This is needed for running U-Boot under virtualization with QEMU/kvm.
--- board/emulation/qemu-arm/qemu-arm.c | 7 +++++++ 1 file changed, 7 insertions(+)
board/emulation/qemu-arm/qemu-arm.c +7 -0
@@ -4,6 +4,7 @@*/ #include <common.h> +#include <cpu_func.h> #include <dm.h> #include <fdtdec.h> #include <init.h>
@@ -94,6 +95,12 @@ void *board_fdt_blob_setup(void)return (void *)CONFIG_SYS_SDRAM_BASE ; } +void enable_caches (void ) +{ +icache_enable (); +dcache_enable (); +} +#if defined(CONFIG_EFI_RNG_PROTOCOL )#include <efi_loader.h> #include <efi_rng.h>
Signature · 1 line
2.26.2
PATCH v2 4/5 arm: qemu: disable the EFI workaround for older GRUB
In reply to Ard BiesheuvelThe QEMU/mach-virt targeted port of u-boot currently only runs on QEMU under TCG emulation, which does not model the caches at all, and so no users can exist that are relying on the GRUB hack for EFI boot.
We will shortly enable support for running under KVM, but the GRUB hack (which disables all caches without doing cache cleaning by VA during ExitBootServices()) is likely to cause more problems than it solves, given that KVM hosts require correct maintenance if they incorporate non-architected system caches.
So let's disable the GRUB hack by default on the QEMU/mach-virt port.
--- configs/qemu_arm_defconfig | 1 + 1 file changed, 1 insertion(+)
configs/qemu_arm_defconfig +1 -0
@@ -47,3 +47,4 @@ CONFIG_USB=y CONFIG_DM_USB=y CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_PCI=y +# CONFIG_EFI_GRUB_ARM32_WORKAROUND is not set
Signature · 1 line
2.26.2
PATCH v2 5/5 arm: qemu: override flash accessors to use virtualizable instructions
In reply to Ard BiesheuvelSome instructions in the ARM ISA have multiple output registers, such as ldrd/ldp (load pair), where two registers are loaded from memory, but also ldr with indexing, where the memory base register is incremented as well when the value is loaded to the destination register.
MMIO emulation under KVM is based on using the architecturally defined syndrome information that is provided when an exception is taken to the hypervisor. This syndrome information describes whether the instruction that triggered the exception is a load or a store, what the faulting address was, and which register was the destination register.
This syndrome information can only describe one destination register, and when the trapping instruction is one with multiple outputs, KVM throws an error like
kvm [615929]: Data abort outside memslots with no valid syndrome info
on the host and kills the QEMU process with the following error:
U-Boot 2020.07-rc3-00208-g88bd5b179360-dirty (Jun 06 2020 - 11:59:22 +0200)
DRAM: 1 GiB
Flash: error: kvm run failed Function not implemented R00=00000001 R01=00000040 R02=7ee0ce20 R03=00000000 R04=7ffd9eec R05=00000004 R06=7ffda3f8 R07=00000055 R08=7ffd9eec R09=7ef0ded0 R10=7ee0ce20 R11=00000000 R12=00000004 R13=7ee0cdf8 R14=00000000 R15=7ff72d08 PSR=200001d3 --C- A svc32
QEMU: Terminated
This means that, in order to run U-Boot in QEMU under KVM, we need to avoid such instructions when accessing emulated devices. For the flash in particular, which is a hybrid between a ROM (backed by a read-only KVM memslot) when in array mode, and an emulated MMIO device (when in write mode), we need to take care to only use instructions that KVM can deal with when they trap.
So override the flash read accessors that are used when running on QEMU under KVM. Note that the the 64-bit wide read accessors and all the write accessors have been omitted: they are either never used to begin with, or don't suffer from the MMIO emulation issue (as str instructions don't have multiple output registers)
--- board/emulation/qemu-arm/qemu-arm.c | 30 ++++++++++++++++++++ include/configs/qemu-arm.h | 1 + 2 files changed, 31 insertions(+)
board/emulation/qemu-arm/qemu-arm.c +30 -0
@@ -142,3 +142,33 @@ efi_status_t platform_get_rng_device(struct udevice **dev)return EFI_SUCCESS ; }#endif /* CONFIG_EFI_RNG_PROTOCOL */ + +#ifdef CONFIG_ARM64 +#define __W "w" +#else +#define __W +#endif + +u8 flash_read8 (void *addr) +{ +u8 ret; + + asm("ldrb %" __W"0, %1" :"=r" (ret) :"m" (*(u8 *)addr)); +return ret; +} + +u16 flash_read16 (void *addr) +{ +u16 ret; + + asm("ldrh %" __W"0, %1" :"=r" (ret) :"m" (*(u16 *)addr)); +return ret; +} + +u32 flash_read32 (void *addr) +{ +u32 ret; + + asm("ldr %" __W"0, %1" :"=r" (ret) :"m" (*(u32 *)addr)); +return ret; +}
include/configs/qemu-arm.h +1 -0
@@ -53,5 +53,6 @@#define CONFIG_SYS_MAX_FLASH_BANKS 2#endif #define CONFIG_SYS_MAX_FLASH_SECT 256/* Sector: 256K, Bank: 64M */ +#define CONFIG_CFI_FLASH_USE_WEAK_ACCESSORS #endif /* __CONFIG_H */
Signature · 1 line
2.26.2
PATCH v2 5/5 arm: qemu: override flash accessors to use virtualizable instructions
Quoted 38 lines · Ard Biesheuvel
Some instructions in the ARM ISA have multiple output registers, such as ldrd/ldp (load pair), where two registers are loaded from memory, but also ldr with indexing, where the memory base register is incremented as well when the value is loaded to the destination register.
MMIO emulation under KVM is based on using the architecturally defined syndrome information that is provided when an exception is taken to the hypervisor. This syndrome information describes whether the instruction that triggered the exception is a load or a store, what the faulting address was, and which register was the destination register.
This syndrome information can only describe one destination register, and when the trapping instruction is one with multiple outputs, KVM throws an error like
kvm [615929]: Data abort outside memslots with no valid syndrome info
on the host and kills the QEMU process with the following error:
U-Boot 2020.07-rc3-00208-g88bd5b179360-dirty (Jun 06 2020 - 11:59:22 +0200)
DRAM: 1 GiB
Flash: error: kvm run failed Function not implemented R00=00000001 R01=00000040 R02=7ee0ce20 R03=00000000 R04=7ffd9eec R05=00000004 R06=7ffda3f8 R07=00000055 R08=7ffd9eec R09=7ef0ded0 R10=7ee0ce20 R11=00000000 R12=00000004 R13=7ee0cdf8 R14=00000000 R15=7ff72d08 PSR=200001d3 --C- A svc32
QEMU: TerminatedThis means that, in order to run U-Boot in QEMU under KVM, we need to avoid such instructions when accessing emulated devices. For the flash in particular, which is a hybrid between a ROM (backed by a read-only KVM memslot) when in array mode, and an emulated MMIO device (when in write mode), we need to take care to only use instructions that KVM can deal with when they trap.
Quoted 6 lines
So override the flash read accessors that are used when running on QEMU under KVM. Note that the the 64-bit wide read accessors and all the write accessors have been omitted: they are either never used to begin with, or don't suffer from the MMIO emulation issue (as str instructions don't have multiple output registers)
This is inaccurate: str instructions do not have multiple output registers, but they may have an output register (for pre/post increment) as well as an input register (for the value being stored), and this cannot be described by the syndrome information. So I will need to respin this once more.
Quoted 58 lines
Signed-off-by Ard Biesheuvel <[email protected]>--- board/emulation/qemu-arm/qemu-arm.c | 30 ++++++++++++++++++++ include/configs/qemu-arm.h | 1 + 2 files changed, 31 insertions(+)board/emulation/qemu-arm/qemu-arm.c +30
-0@@ -142,3 +142,33 @@ efi_status_t platform_get_rng_device(struct udevice **dev)return EFI_SUCCESS ; }#endif /* CONFIG_EFI_RNG_PROTOCOL */ + +#ifdef CONFIG_ARM64 +#define __W "w" +#else +#define __W +#endif + +u8 flash_read8 (void *addr) +{ +u8 ret; + + asm("ldrb %" __W"0, %1" :"=r" (ret) :"m" (*(u8 *)addr)); +return ret; +} + +u16 flash_read16 (void *addr) +{ +u16 ret; + + asm("ldrh %" __W"0, %1" :"=r" (ret) :"m" (*(u16 *)addr)); +return ret; +} + +u32 flash_read32 (void *addr) +{ +u32 ret; + + asm("ldr %" __W"0, %1" :"=r" (ret) :"m" (*(u32 *)addr)); +return ret; +}include/configs/qemu-arm.h +1
-1@@ -53,5 +53,6 @@#define CONFIG_SYS_MAX_FLASH_BANKS 2#endif #define CONFIG_SYS_MAX_FLASH_SECT 256/* Sector: 256K, Bank: 64M */ +#define CONFIG_CFI_FLASH_USE_WEAK_ACCESSORS #endif /* __CONFIG_H */ --2.26.2