hw/riscv: virt: Enable booting S-mode firmware from pflash
v2 cover hw/riscv: virt: Enable booting S-mode firmware from pflash
This series adds the support to boot S-mode FW like EDK2 from the flash. The S-mode firmware should be kept in pflash unit 1.
When -kernel (and -initrd) option is also provided along with the flash, the kernel (and initrd) will be loaded into fw_cfg table and opensbi will branch to the flash address which will be the entry point of the S-mode firmware. The S-mode FW then loads and launches the kernel.
When only -pflash option is provided in the command line, the kernel will be located and loaded in the usual way by the S-mode firmware.
These patches are available in below branch.
https://github.com/vlsunil/qemu/tree/pflash_v2
The first two patches in this series are refactor patches.
These changes are tested with a WIP EDK2 port for virt machine. Below are the instructions to build and test this feature.
1) Get EDK2 sources from below branches.
https://github.com/vlsunil/edk2/tree/virt_refactor_smode_v1
https://github.com/vlsunil/edk2-platforms/tree/virt_refactor_smode_v1
2) Build EDK2 for RISC-V
export WORKSPACE=pwd
export GCC5_RISCV64_PREFIX=riscv64-linux-gnu-
export PACKAGES_PATH=$WORKSPACE/edk2:$WORKSPACE/edk2-platforms export EDK_TOOLS_PATH=$WORKSPACE/edk2/BaseTools
source edk2/edksetup.sh
make -C edk2/BaseTools clean
make -C edk2/BaseTools
make -C edk2/BaseTools/Source/C
source edk2/edksetup.sh BaseTools
build -a RISCV64 -p Platform/Qemu/RiscVVirt/RiscVVirt.dsc -t GCC5
3)Make the EDK2 image size to match with what qemu flash expects truncate -s 32M Build/RiscVVirt/DEBUG_GCC5/FV/RISCV_VIRT.fd
4) Run
a) Boot to EFI shell (no -kernel / -initrd option)
qemu-system-riscv64 -nographic -drive file=Build/RiscVVirt/DEBUG_GCC5/FV/RISCV_VIRT.fd,if=pflash,format=raw,unit=1 -machine virt -M 2G
b) With -kernel, -initrd and -pflash
qemu-system-riscv64 -nographic -drive file=Build/RiscVVirt/DEBUG_GCC5/FV/RISCV_VIRT.fd,if=pflash,format=raw,unit=1 -machine virt -M 2G -kernel arch/riscv/boot/Image.gz -initrd rootfs.cpio
Changes since V1:
1) Modified code to support the use case when both -kernel and -pflash are configured.
2) Refactor patches added to help (1) above.
3) Cover letter added with test instructions.
Sunil V L (3):
hw/arm,loongarch: Move load_image_to_fw_cfg() to common location hw/riscv: virt: Move create_fw_cfg() prior to loading kernel hw/riscv: virt: Enable booting S-mode firmware from pflash
hw/arm/boot.c | 49 --------------------------------------- hw/loongarch/virt.c | 33 -------------------------- hw/nvram/fw_cfg.c | 49 +++++++++++++++++++++++++++++++++++++++ hw/riscv/boot.c | 28 ++++++++++++++++++++++ hw/riscv/virt.c | 31 ++++++++++++++++++------- include/hw/nvram/fw_cfg.h | 3 +++ include/hw/riscv/boot.h | 1 + 7 files changed, 104 insertions(+), 90 deletions(-)
Signature · 1 line
2.25.1
PATCH v2 1/3 hw/arm, loongarch: Move load_image_to_fw_cfg() to common location
load_image_to_fw_cfg() is duplicated by both arm and loongarch. The same function will be required by riscv too. So, it's time to refactor and move this function to a common path.
--- hw/arm/boot.c | 49 --------------------------------------- hw/loongarch/virt.c | 33 -------------------------- hw/nvram/fw_cfg.c | 49 +++++++++++++++++++++++++++++++++++++++ include/hw/nvram/fw_cfg.h | 3 +++ 4 files changed, 52 insertions(+), 82 deletions(-)
hw/arm/boot.c +0 -49
@@ -818,55 +818,6 @@ static void do_cpu_reset(void *opaque) } } -/** -* load_image_to_fw_cfg() - Load an image file into an fw_cfg entry identified -* by key. -* @fw_cfg: The firmware config instance to store the data in. -* @size_key: The firmware config key to store the size of the loaded -* data under, with fw_cfg_add_i32(). -* @data_key: The firmware config key to store the loaded data under, -* with fw_cfg_add_bytes(). -* @image_name: The name of the image file to load. If it is NULL, the -* function returns without doing anything. -* @try_decompress: Whether the image should be decompressed (gunzipped) before -* adding it to fw_cfg. If decompression fails, the image is -* loaded as-is. -* -* In case of failure, the function prints an error message to stderr and the -* process exits with status 1. -*/ -static void load_image_to_fw_cfg (FWCfgState *fw_cfg,uint16_t size_key, -uint16_t data_key,const char *image_name, -bool try_decompress) -{ -size_t size =-1 ; -uint8_t *data; - -if (image_name ==NULL ) { -return ; - } - -if (try_decompress) { - size =load_image_gzipped_buffer (image_name, -LOAD_IMAGE_MAX_GUNZIP_BYTES , &data); - } - -if (size == (size_t )-1 ) { -gchar *contents; -gsize length; - -if (!g_file_get_contents (image_name, &contents, &length,NULL )) { -error_report ("failed to load \"%s\"" , image_name); -exit (1 ); - } - size = length; - data = (uint8_t *)contents; - } - -fw_cfg_add_i32 (fw_cfg, size_key, size); -fw_cfg_add_bytes (fw_cfg, data_key, data, size); -} -static int do_arm_linux_init (Object *obj,void *opaque) {if (object_dynamic_cast (obj,TYPE_ARM_LINUX_BOOT_IF )) {
hw/loongarch/virt.c +0 -33
@@ -542,39 +542,6 @@ static void reset_load_elf(void *opaque) } } -/* Load an image file into an fw_cfg entry identified by key. */ -static void load_image_to_fw_cfg (FWCfgState *fw_cfg,uint16_t size_key, -uint16_t data_key,const char *image_name, -bool try_decompress) -{ -size_t size =-1 ; -uint8_t *data; - -if (image_name ==NULL ) { -return ; - } - -if (try_decompress) { - size =load_image_gzipped_buffer (image_name, -LOAD_IMAGE_MAX_GUNZIP_BYTES , &data); - } - -if (size == (size_t )-1 ) { -gchar *contents; -gsize length; - -if (!g_file_get_contents (image_name, &contents, &length,NULL )) { -error_report ("failed to load \"%s\"" , image_name); -exit (1 ); - } - size = length; - data = (uint8_t *)contents; - } - -fw_cfg_add_i32 (fw_cfg, size_key, size); -fw_cfg_add_bytes (fw_cfg, data_key, data, size); -} -static void fw_cfg_add_kernel_info (FWCfgState *fw_cfg) {/*
hw/nvram/fw_cfg.c +49 -0
61 lines not on this page · raw message
include/hw/nvram/fw_cfg.h +3 -0
@@ -341,5 +341,8 @@ bool fw_cfg_dma_enabled(void *opaque);* key lookup failure. */ const char *fw_cfg_arch_key_name (uint16_t key); +void load_image_to_fw_cfg (FWCfgState *fw_cfg,uint16_t size_key, +uint16_t data_key,const char *image_name, +bool try_decompress);#endif
Signature · 1 line
2.25.1
Re: [PATCH V2 1/3] hw/arm,loongarch: Move load_image_to_fw_cfg() to common location
Quoted 27 lines · Sunil V L
load_image_to_fw_cfg()is duplicated by both arm and loongarch. The same function will be required by riscv too. So, it's time to refactor and move this function to a common path.Signed-off-by Sunil V L <[email protected]>--- hw/arm/boot.c | 49 --------------------------------------- hw/loongarch/virt.c | 33 -------------------------- hw/nvram/fw_cfg.c | 49 +++++++++++++++++++++++++++++++++++++++ include/hw/nvram/fw_cfg.h | 3 +++ 4 files changed, 52 insertions(+), 82 deletions(-)hw/nvram/fw_cfg.c +1
-0@@ -41,6 +41,7 @@#include "qapi/error.h" #include "hw/acpi/aml-build.h" #include "hw/pci/pci_bus.h" +#include "hw/loader.h" #define FW_CFG_FILE_SLOTS_DFLT 0x20
hw/nvram/fw_cfg.c FWCfgState *fw_cfg_find(void) · line 1227
Quoted 6 lines
hw/nvram/fw_cfg.c +3
-0@@ -1221,6 +1222,54 @@ FWCfgState *fw_cfg_find(void)return FW_CFG (object_resolve_path_type ("" ,TYPE_FW_CFG ,NULL )); } +/** +* load_image_to_fw_cfg() - Load an image file into an fw_cfg entry identified +* by key.
For functions declared in public header files, put the doc comment in the .h file, not the .c file, please.
thanks
-- PMM
Re: [PATCH V2 1/3] hw/arm,loongarch: Move load_image_to_fw_cfg() to common location
Quoted 31 lines · Peter Maydell
Quoted 30 lines · Sunil V L
load_image_to_fw_cfg()is duplicated by both arm and loongarch. The same function will be required by riscv too. So, it's time to refactor and move this function to a common path.Signed-off-by Sunil V L <[email protected]>--- hw/arm/boot.c | 49 --------------------------------------- hw/loongarch/virt.c | 33 -------------------------- hw/nvram/fw_cfg.c | 49 +++++++++++++++++++++++++++++++++++++++ include/hw/nvram/fw_cfg.h | 3 +++ 4 files changed, 52 insertions(+), 82 deletions(-)hw/nvram/fw_cfg.c +1
-0@@ -41,6 +41,7 @@#include "qapi/error.h" #include "hw/acpi/aml-build.h" #include "hw/pci/pci_bus.h" +#include "hw/loader.h" #define FW_CFG_FILE_SLOTS_DFLT 0x20@@ -1221,6 +1222,54 @@ FWCfgState *fw_cfg_find(void)return FW_CFG (object_resolve_path_type ("" ,TYPE_FW_CFG ,NULL )); }
Quoted 6 lines
hw/nvram/fw_cfg.c FWCfgState *fw_cfg_find(void) · line 1227
Quoted 3 lines
hw/nvram/fw_cfg.c +3
-0+/** +* load_image_to_fw_cfg() - Load an image file into an fw_cfg entry identified +* by key. For functions declared in public header files, put the doc comment in the .h file, not the .c file, please.
Thanks! Peter. Will send V3 with this change.
Thanks
Sunil
Quoted 3 lines
thanks
-- PMM
PATCH v2 2/3 hw/riscv: virt: Move create_fw_cfg() prior to loading kernel
In reply to Sunil V LTo enable both -kernel and -pflash options, the fw_cfg needs to be created prior to loading the kernel.
--- hw/riscv/virt.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
hw/riscv/virt.c +7 -7
@@ -1251,6 +1251,13 @@ static void virt_machine_done(Notifier *notifier, void *data) RISCV64_BIOS_BIN, start_addr, NULL); } +/* +* Init fw_cfg. Must be done before riscv_load_fdt, otherwise the device +* tree cannot be altered and we get FDT_ERR_NOSPACE. +*/ + s->fw_cfg =create_fw_cfg (machine); +rom_set_fw (s->fw_cfg); +if (machine->kernel_filename) { kernel_start_addr =riscv_calc_kernel_start_addr (&s->soc[0 ], firmware_end_addr);
@@ -1284,13 +1291,6 @@ static void virt_machine_done(Notifier *notifier, void *data) start_addr = virt_memmap[VIRT_FLASH ].base; } -/* -* Init fw_cfg. Must be done before riscv_load_fdt, otherwise the device -* tree cannot be altered and we get FDT_ERR_NOSPACE. -*/ - s->fw_cfg =create_fw_cfg (machine); -rom_set_fw (s->fw_cfg); -/* Compute the fdt load address in dram */ fdt_load_addr =riscv_load_fdt (memmap[VIRT_DRAM ].base, machine->ram_size, machine->fdt);
Signature · 1 line
2.25.1
PATCH v2 3/3 hw/riscv: virt: Enable booting S-mode firmware from pflash
In reply to Sunil V LTo boot S-mode firmware payload like EDK2 from persistent flash storage, qemu needs to pass the flash address as the next_addr in fw_dynamic_info to the opensbi.
When both -kernel and -pflash options are provided in command line, the kernel (and initrd if -initrd) will be copied to fw_cfg table. The S-mode FW will load the kernel/initrd from fw_cfg table.
If only pflash is given but not -kernel, then it is the job of of the S-mode firmware to locate and load the kernel.
In either case, update the kernel_entry with the flash address so that the opensbi can jump to the entry point of the S-mode firmware.
--- hw/riscv/boot.c | 28 ++++++++++++++++++++++++++++ hw/riscv/virt.c | 17 ++++++++++++++++- include/hw/riscv/boot.h | 1 + 3 files changed, 45 insertions(+), 1 deletion(-)
hw/riscv/boot.c +28 -0
@@ -338,3 +338,31 @@ void riscv_setup_direct_kernel(hwaddr kernel_addr, hwaddr fdt_addr) riscv_cpu->env.fdt_addr = fdt_addr; } } + +void riscv_setup_firmware_boot (MachineState *machine) +{ +if (machine->kernel_filename) { +FWCfgState *fw_cfg; + fw_cfg =fw_cfg_find (); + +assert (fw_cfg); +/* +* Expose the kernel, the command line, and the initrd in fw_cfg. +* We don't process them here at all, it's all left to the +* firmware. +*/ +load_image_to_fw_cfg (fw_cfg, +FW_CFG_KERNEL_SIZE ,FW_CFG_KERNEL_DATA , + machine->kernel_filename, + true); +load_image_to_fw_cfg (fw_cfg, +FW_CFG_INITRD_SIZE ,FW_CFG_INITRD_DATA , + machine->initrd_filename, false); +if (machine->kernel_cmdline) { +fw_cfg_add_i32 (fw_cfg,FW_CFG_CMDLINE_SIZE , +strlen (machine->kernel_cmdline) +1 ); +fw_cfg_add_string (fw_cfg,FW_CFG_CMDLINE_DATA , + machine->kernel_cmdline); + } + } +}
hw/riscv/virt.c +16 -1
@@ -1258,7 +1258,22 @@ static void virt_machine_done(Notifier *notifier, void *data) s->fw_cfg =create_fw_cfg (machine);rom_set_fw (s->fw_cfg); -if (machine->kernel_filename) { +if (drive_get (IF_PFLASH ,0 ,1 )) { +/* +* S-mode FW like EDk2 will be kept in second plash (unit 1). When +* both -kernel and -pflash options are provided in command line, +* the kernel, initrd will be copied to fw_cfg table and opensbi +* will jump to flash address which is the entry point of S-mode FW. +* It is the job of the S-mode FW to load the kernel/initrd and launch. +* +* If only pflash is given but not -kernel, then it is the job of +* of the S-mode firmware to locate and load the kernel. +* In either case, the next_addr for opensbi will be the flash address. +*/ +riscv_setup_firmware_boot (machine); + kernel_entry = virt_memmap[VIRT_FLASH ].base + + virt_memmap[VIRT_FLASH ].size /2 ; + }else if (machine->kernel_filename) { kernel_start_addr =riscv_calc_kernel_start_addr (&s->soc[0 ], firmware_end_addr);
include/hw/riscv/boot.h +1 -0
@@ -57,5 +57,6 @@ void riscv_rom_copy_firmware_info(MachineState *machine, hwaddr rom_base,uint32_t reset_vec_size, uint64_t kernel_entry);void riscv_setup_direct_kernel (hwaddr kernel_addr,hwaddr fdt_addr); +void riscv_setup_firmware_boot (MachineState *machine);#endif /* RISCV_BOOT_H */
Signature · 1 line
2.25.1