All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ewan Hai-oc" <ewanhai-oc@zhaoxin.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v3 4/5] KVM: x86: Expose Zhaoxin PHE2 CPUID feature
Date: Wed, 10 Jun 2026 02:45:17 +0000	[thread overview]
Message-ID: <20260610024518.3F95D1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260610023512.3690734-5-ewanhai-oc@zhaoxin.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch adds X86_FEATURE_PHE2 and X86_FEATURE_PHE2_EN to arch/x86/include/asm/cpufeatures.h but fails to update the corresponding tools header tools/arch/x86/include/asm/cpufeatures.h.
--

commit 3f9973df29d33e555520e65352e2ad0d4e602e77
Author: Ewan Hai-oc <ewanhai-oc@zhaoxin.com>

KVM: x86: Expose Zhaoxin PHE2 CPUID feature

This commit advertises the Zhaoxin PadLock Hash Engine v2 to guests via
CPUID 0xC0000001 EDX bits 25 and 26. It exposes unprivileged instructions
for SHA-384 and SHA-512 support.

> diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h
> index e264758d58e22..3702d7a30ae61 100644
> --- a/arch/x86/include/asm/cpufeatures.h
> +++ b/arch/x86/include/asm/cpufeatures.h
> @@ -152,6 +152,8 @@
>  #define X86_FEATURE_PMM_EN		( 5*32+13) /* "pmm_en" PMM enabled */
>  #define X86_FEATURE_RNG2		( 5*32+22) /* "rng2" RNG v2 */
>  #define X86_FEATURE_RNG2_EN		( 5*32+23) /* "rng2_en" RNG2 enabled */
> +#define X86_FEATURE_PHE2		( 5*32+25) /* "phe2" PadLock Hash Engine v2 */
> +#define X86_FEATURE_PHE2_EN		( 5*32+26) /* "phe2_en" PHE2 enabled */

[Severity: Low]
Is it necessary to synchronize this addition with the tooling headers?

Adding new feature bits to arch/x86/include/asm/cpufeatures.h without also
mirroring them to tools/arch/x86/include/asm/cpufeatures.h usually causes
check-headers.sh to emit a build warning in the tools/perf tree.

Could this patch include the update to the tools directory copy to prevent
these warnings?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260610023512.3690734-1-ewanhai-oc@zhaoxin.com?part=4

  reply	other threads:[~2026-06-10  2:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  2:35 [PATCH v3 0/5] KVM: x86: Expose Zhaoxin CPUID 0xC0000001 EDX cryptographic features Ewan Hai-oc
2026-06-10  2:35 ` [PATCH v3 1/5] KVM: x86: Expose Zhaoxin SM2 CPUID feature Ewan Hai-oc
2026-06-10  2:43   ` sashiko-bot
2026-06-10  2:35 ` [PATCH v3 2/5] KVM: x86: Expose Zhaoxin CCS (SM3 + SM4) " Ewan Hai-oc
2026-06-10  2:42   ` sashiko-bot
2026-06-10  2:35 ` [PATCH v3 3/5] KVM: x86: Expose Zhaoxin RNG2 " Ewan Hai-oc
2026-06-10  2:44   ` sashiko-bot
2026-06-10  2:35 ` [PATCH v3 4/5] KVM: x86: Expose Zhaoxin PHE2 " Ewan Hai-oc
2026-06-10  2:45   ` sashiko-bot [this message]
2026-06-10  2:35 ` [PATCH v3 5/5] KVM: x86: Expose Zhaoxin RSA " Ewan Hai-oc
2026-07-01  2:45 ` [PATCH v3 0/5] KVM: x86: Expose Zhaoxin CPUID 0xC0000001 EDX cryptographic features Ewan Hai-oc
2026-07-01 14:09   ` Sean Christopherson
2026-07-02  1:49     ` Borislav Petkov
2026-07-02  3:27       ` Ewan Hai-oc
2026-07-06 14:38       ` Sean Christopherson
2026-07-06 17:00         ` Borislav Petkov

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=20260610024518.3F95D1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ewanhai-oc@zhaoxin.com \
    --cc=kvm@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.