opensbi.git/firmware, branch v0.6

firmware: Fix placement of .align directives

2020-01-10T04:00:27Z

Move the .align directives after switching the section. We want to align the start of the current section, not the end of the previous section. This also obsoletes the misguided workaround of disabling relaxation. Signed-off-by: Andreas Schwab Reviewed-by: Anup Patel

firmware: Improve comments for fw_prev_arg1() and fw_next_arg1()

2019-12-27T03:24:24Z

The state of a0, a1, and a2 registers in fw_prev_arg1() and fw_next_arg1() is same as passed by previous booting stage so we add this info in comments for both these functions. Signed-off-by: Anup Patel

firmware: Return real DTB address when FW_xyz_FDT_ADDR is not defined

2019-12-27T03:18:17Z

Function fw_next_arg1 in firmware/fw_jump.S:59 and firmware/fw_payload.S:63 should return real dtb address(if specified in a1) in a0, in case we don't want to specify FW_xyz_FDT_ADDR when compiling. Signed-off-by: Liu Yibin Reviewed-by: Anup Patel

firmware: Add preferred boot HART field in struct fw_dynamic_info

2019-11-15T12:11:18Z

It has been reported that link address range of previous booting stage (such as U-Boot SPL) can overlap the link address rage of FW_DYNAMIC. This means self-relocation in FW_DYNAMIC can potentially corrupt previous booting stage if any of the secondary HART enter FW_DYNAMIC before primary HART. To tackle this, we add preferred boot HART field (i.e boot_hart) in struct fw_dyanmic_info. We use this field to force secondary HARTs into relocation wait loop till preferred/primary boot HART enters FW_DYNAMIC completes self-relocation. If preferred boot HART is not available then we fall back to relocation lottery approach. Signed-off-by: Anup Patel Reviewed-by: Atish Patra

firmware: Introduce relocation lottery

2019-11-05T03:20:04Z

Instead of forcing HART0 to do the relocation and scratch init work, we should have an atomic lottery to decide which HART does the relocation and scratch init. This way any HART can be boot/main HART. Signed-off-by: Anup Patel Reviewed-by: Atish Patra

firmware: Fix compile error for FW_PAYLOAD with latest GCC binutils

2019-10-28T14:41:42Z

We get following compile error for FW_PAYLOAD with latest GCC binutils: fw_payload.o(.text+0x1961): 15 bytes required for alignment to 16-byte boundary, but only 14 present Further investigating, it turn-out to be a known issue with RISC-V GCC binutils. (Refer, https://github.com/riscv/riscv-gnu-toolchain/issues/298) As a work-around, we disable relaxation when including DTB and PAYLOAD binary in fw_payload.S. Reported-by: David Abdurachmanov Signed-off-by: Anup Patel Tested-by: David Abdurachmanov Reviewed-by: Atish Patra

lib: Rename existing SBI implementation as 0.1.

2019-10-03T03:23:52Z

Current SBI implementation is now considered as version 0.1 and will be removed/replaced with newer extension/functions in future. Rename the existing implementations accordingly to be in sync with the specification. Signed-off-by: Atish Patra Reviewed-by: Anup Patel Reviewed-by: Zong Li

Test: Move test payload related code out of interface header

2019-10-03T03:21:39Z

Test payload uses an SBI call and uses the macros defined in interface header which is not the correct place to have these definitions. The interface header file should be used to keep SBI specification related macros. Keep all the test payload related code in test itself. Signed-off-by: Atish Patra Reviewed-by: Anup Patel

lib: Extend sbi_trap_redirect() for hypervisor extension

2019-09-30T09:59:37Z

When hypervisor extension is available, we can get traps from VS/VU modes. We should be able to force redirect some of these traps to HS-mode. In other words, we should be able forward traps from VS/VU mode to HS-mode using sbi_trap_redirect() hence this patch. Signed-off-by: Atish Patra Signed-off-by: Anup Patel Signed-off-by: Alistair Francis

firmware: do not use relocated _boot_status before it is valid

2019-08-13T03:37:16Z

When OpenSBI is started from an address not equal to the link address, it is first relocated to the link address. Hart 0 performs the relocation and notifies the other harts of its completion with the _boot_status variable. It uses the copy of the variable relative to the link address. This copy contains valid data only after relocation has finished. The waiting harts will therefore read invalid data until relocation has finished. This can cause them to continue execution too early. Fix this by using the _boot_status variable relative to the load address while OpenSBI has not finished relocation. Signed-off-by: Lukas Auer Reviewed-by: Anup Patel