From: Sean Christopherson <seanjc@google.com>
To: Ewan Hai <ewanhai-oc@zhaoxin.com>
Cc: pbonzini@redhat.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, ewanhai@zhaoxin.com,
cobechen@zhaoxin.com, leoliu@zhaoxin.com, lyleli@zhaoxin.com
Subject: Re: [PATCH] KVM: x86: expose CPUID 0xC000_0000 for Zhaoxin "Shanghai" vendor
Date: Tue, 12 Aug 2025 08:07:01 -0700 [thread overview]
Message-ID: <aJtYlfuBSWhXS3dW@google.com> (raw)
In-Reply-To: <20250811013558.332940-1-ewanhai-oc@zhaoxin.com>
On Sun, Aug 10, 2025, Ewan Hai wrote:
> rename the local constant CENTAUR_CPUID_SIGNATURE to ZHAOXIN_CPUID_SIGNATURE.
Why? I'm not inclined to rename any of the Centaur references, as I don't see
any point in effectively rewriting history. If we elect to rename things, then
it needs to be done in a separate patch, there needs to be proper justification,
and _all_ references should be converted, e.g. converting just this one macro
creates discrepancies even with cpuid.c, as there are multiple comments that
specifically talk about Centaur CPUID leaves.
> The constant is used only inside cpuid.c, so the rename is NFC outside this
> file.
>
> Signed-off-by: Ewan Hai <ewanhai-oc@zhaoxin.com>
> ---
> arch/x86/kvm/cpuid.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
> index e2836a255b16..beb83eaa1868 100644
> --- a/arch/x86/kvm/cpuid.c
> +++ b/arch/x86/kvm/cpuid.c
> @@ -1811,7 +1811,7 @@ static int do_cpuid_func(struct kvm_cpuid_array *array, u32 func,
> return __do_cpuid_func(array, func);
> }
>
> -#define CENTAUR_CPUID_SIGNATURE 0xC0000000
> +#define ZHAOXIN_CPUID_SIGNATURE 0xC0000000
>
> static int get_cpuid_func(struct kvm_cpuid_array *array, u32 func,
> unsigned int type)
> @@ -1819,8 +1819,9 @@ static int get_cpuid_func(struct kvm_cpuid_array *array, u32 func,
> u32 limit;
> int r;
>
> - if (func == CENTAUR_CPUID_SIGNATURE &&
> - boot_cpu_data.x86_vendor != X86_VENDOR_CENTAUR)
> + if (func == ZHAOXIN_CPUID_SIGNATURE &&
> + boot_cpu_data.x86_vendor != X86_VENDOR_CENTAUR &&
> + boot_cpu_data.x86_vendor != X86_VENDOR_ZHAOXIN)
Align indentation.
if (func == CENTAUR_CPUID_SIGNATURE &&
boot_cpu_data.x86_vendor != X86_VENDOR_CENTAUR &&
boot_cpu_data.x86_vendor != X86_VENDOR_ZHAOXIN)
return 0;
> return 0;
>
> r = do_cpuid_func(array, func, type);
> @@ -1869,7 +1870,7 @@ int kvm_dev_ioctl_get_cpuid(struct kvm_cpuid2 *cpuid,
> unsigned int type)
> {
> static const u32 funcs[] = {
> - 0, 0x80000000, CENTAUR_CPUID_SIGNATURE, KVM_CPUID_SIGNATURE,
> + 0, 0x80000000, ZHAOXIN_CPUID_SIGNATURE, KVM_CPUID_SIGNATURE,
> };
>
> struct kvm_cpuid_array array = {
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-08-12 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 1:35 Ewan Hai
2025-08-12 15:07 ` Sean Christopherson [this message]
2025-08-13 8:38 ` Ewan Hai
2025-08-16 0:29 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aJtYlfuBSWhXS3dW@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=cobechen@zhaoxin.com \
--cc=dave.hansen@linux.intel.com \
--cc=ewanhai-oc@zhaoxin.com \
--cc=ewanhai@zhaoxin.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=leoliu@zhaoxin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyleli@zhaoxin.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®