From: sashiko-bot@kernel.org
To: "Ewan Hai-oc" <ewanhai-oc@zhaoxin.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v3 3/5] KVM: x86: Expose Zhaoxin RNG2 CPUID feature
Date: Wed, 10 Jun 2026 02:44:16 +0000 [thread overview]
Message-ID: <20260610024416.D811C1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260610023512.3690734-4-ewanhai-oc@zhaoxin.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing synchronization of tools/arch/x86/include/asm/cpufeatures.h.
--
commit 0ff90b8c977a44dc52de6838a89fc982a023995b
Author: Ewan Hai-oc <ewanhai-oc@zhaoxin.com>
KVM: x86: Expose Zhaoxin RNG2 CPUID feature
This commit advertises the Zhaoxin second-generation hardware RNG
to guests via CPUID 0xC0000001 EDX bits 22 and 23. It adds the
corresponding feature definitions and initializes them in the
capabilities list.
> diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h
> index 276e4ef90bd07..e264758d58e22 100644
> --- a/arch/x86/include/asm/cpufeatures.h
> +++ b/arch/x86/include/asm/cpufeatures.h
> @@ -150,6 +150,8 @@
> #define X86_FEATURE_PHE_EN ( 5*32+11) /* "phe_en" PHE enabled */
> #define X86_FEATURE_PMM ( 5*32+12) /* "pmm" PadLock Montgomery Multiplier */
> #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 */
[Severity: Low]
Does this change also need to be synchronized to
tools/arch/x86/include/asm/cpufeatures.h?
Leaving the tools header unsynchronized typically results in a build
warning from tools/perf/check-headers.sh when checking for divergences.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260610023512.3690734-1-ewanhai-oc@zhaoxin.com?part=3
next prev parent reply other threads:[~2026-06-10 2:44 UTC|newest]
Thread overview: 10+ 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 [this message]
2026-06-10 2:35 ` [PATCH v3 4/5] KVM: x86: Expose Zhaoxin PHE2 " Ewan Hai-oc
2026-06-10 2:45 ` sashiko-bot
2026-06-10 2:35 ` [PATCH v3 5/5] KVM: x86: Expose Zhaoxin RSA " Ewan Hai-oc
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=20260610024416.D811C1F00893@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox