On Thu, Jul 30, 2026, Ewan Hai-oc wrote:
> From: Frank Zhu <[email protected]>
>
> Add infrastructure to detect Zhaoxin CPUs in KVM selftests. Zhaoxin
> CPUs use vendor strings "CentaurHauls" or " Shanghai " and implement
> VMX-compatible virtualization technology.
>
> Signed-off-by: Frank Zhu <[email protected]>
> Signed-off-by: Ewan Hai <[email protected]>
> ---
> tools/testing/selftests/kvm/include/x86/processor.h | 7 +++++++
> tools/testing/selftests/kvm/lib/x86/processor.c | 3 +++
> 2 files changed, 10 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/include/x86/processor.h
> b/tools/testing/selftests/kvm/include/x86/processor.h
> index b161174ece45..9840b583877c 100644
> --- a/tools/testing/selftests/kvm/include/x86/processor.h
> +++ b/tools/testing/selftests/kvm/include/x86/processor.h
> @@ -23,6 +23,7 @@ extern bool host_cpu_is_intel;
> extern bool host_cpu_is_amd;
> extern bool host_cpu_is_hygon;
> extern bool host_cpu_is_amd_compatible;
> +extern bool host_cpu_is_zx;
Please spell out "zhaoxin", "zx" isn't intuitive for most of us (I keep thinking
it's a compression feature).
And do the same thing we did in commit 53b2869231d3 ("KVM: selftests: Add a flag
to identify AMD compatible test cases"), and add host_cpu_is_intel_compatible.
That should cut down on the number of checks on is_zhaoxin, and should help
avoid
issues like the ones Sashiko pointed out.
