This repository hosts unit tests for riscv hypervisor extension.
Testing is done by executing bare metal applications, which set up the environment at different privilege levels, execute the testing code or trigger traps and check the execution results and processor status to determine if specific features of the target platform is compliant with the hypervisor extension specification.
We assume that the RISC-V toolchain is installed and is added to the PATH.
The target platform on which the test will run should be specified by setting the PLAT environment variables. And the platforms that are currently supported are shown in the table below:
| Platform | ${PLAT} Parameters |
|---|---|
| QEMU | qemu |
| Rocket Chip Emulator | rocket_emul |
| Rocket Chip FPGA | rocket_fpga |
| Spike Emulator | spike |
The output level can be specified via the LOG_LEVEL environment variable (default is LOG_INFO).
Options include:
LOG_NONE, LOG_ERROR, LOG_INFO, LOG_DETAIL, LOG_WARNING, LOG_VERBOSE, LOG_DEBUG
The build process is as follows:
$ git clone https://github.com/josecm/riscv-hyp-tests
$ cd riscv-hyp-tests
$ PLAT=${target_platform} makeThe compilation result is located at build/${target_platform}/rvh_test.elf or rvh_test.bin.
scripts/run_on_spike.sh is a script to run on spike
We found that in higher versions of RISC-V gcc than gcc-10, instructions such as csrwi are grouped separately under the zicsr extension and need to be specified explicitly by appending zicsr string to the -march parameter of gcc.
additional relocation overflows omitted from the output or relocation truncated to fit: R_RISCV_HI20
Please check if the currently used RISC-V toolchain is configured with the --with-cmodel=medany parameter.
This can be determined by executing command: riscv64-unknown-elf-gcc -v.
And look at the Configured with: ...... line in the output.