mirror of
https://gitlab.com/buildroot.org/buildroot.git
synced 2026-09-09 07:51:59 -09:00
137d6e249d
Although it is possible to configure an AArch64 CPU without support for EL2 in practice all the common AArch64 have supported virtualisation from the start. If we really wanted to be strict we could blacklist known non-EL2 CPUs but AFAICT all the current ones in the config have EL2. I should also note KVM on Arm is deprecated and was removed from the kernel in v6.10. Reviewed-by: Jesse Taube <jesse@rivosinc.com> Reviewed-by: Thomas Huth <huth@tuxfamily.org> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
46 lines
2.0 KiB
Plaintext
46 lines
2.0 KiB
Plaintext
config BR2_PACKAGE_KVM_UNIT_TESTS_ARCH_SUPPORTS
|
|
bool
|
|
# On ARM, it needs virtualization extensions and little endian CPUs
|
|
default y if BR2_arm && \
|
|
(BR2_cortex_a7 || BR2_cortex_a12 || \
|
|
BR2_cortex_a15 || BR2_cortex_a15_a7 || \
|
|
BR2_cortex_a17 || BR2_cortex_a17_a7 || \
|
|
BR2_cortex_a76 || BR2_cortex_a76_a55)
|
|
# For AArch64 we can assume all v8.0+ support virtualization
|
|
default y if BR2_aarch64
|
|
default y if BR2_riscv
|
|
default y if BR2_i386 || BR2_x86_64
|
|
default y if BR2_powerpc64 || BR2_powerpc64le
|
|
default y if BR2_s390x
|
|
|
|
config BR2_PACKAGE_KVM_UNIT_TESTS
|
|
bool "kvm-unit-tests"
|
|
depends on BR2_PACKAGE_KVM_UNIT_TESTS_ARCH_SUPPORTS
|
|
# on i386 and x86-64, __builtin_reachable is used, so we need
|
|
# gcc 4.5 at least. on i386, we use the target gcc, while on
|
|
# x86-64 we use the host gcc (see .mk file for details)
|
|
depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_5 || !BR2_i386
|
|
depends on BR2_HOSTARCH = "x86_64" || !BR2_x86_64
|
|
select BR2_HOSTARCH_NEEDS_IA32_COMPILER if BR2_x86_64
|
|
help
|
|
kvm-unit-tests is a project as old as KVM. As its name
|
|
suggests, it's purpose is to provide unit tests for KVM. The
|
|
unit tests are tiny guest operating systems that generally
|
|
execute only tens of lines of C and assembler test code in
|
|
order to obtain its PASS/FAIL result. Unit tests provide KVM
|
|
and virt hardware functional testing by targeting the
|
|
features through minimal implementations of their use per
|
|
the hardware specification. The simplicity of unit tests
|
|
make them easy to verify they are correct, easy to maintain,
|
|
and easy to use in timing measurements. Unit tests are also
|
|
often used for quick and dirty bug reproducers. The
|
|
reproducers may then be kept as regression tests. It's
|
|
strongly encouraged that patches implementing new KVM
|
|
features are submitted with accompanying unit tests.
|
|
|
|
http://www.linux-kvm.org/page/KVM-unit-tests
|
|
|
|
comment "kvm-unit-tests needs a toolchain w/ gcc >= 4.5"
|
|
depends on BR2_i386
|
|
depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_4_5
|