From: sashiko-bot@kernel.org
To: "Ashish Kalra" <Ashish.Kalra@amd.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v6 1/6] x86/cpufeatures: Add X86_FEATURE_AMD_RMPOPT feature flag
Date: Tue, 02 Jun 2026 20:10:38 +0000 [thread overview]
Message-ID: <20260602201039.384491F00893@smtp.kernel.org> (raw)
In-Reply-To: <5f587ed487c037ce6a1174fa8cdf25112d2c8eac.1780427587.git.ashish.kalra@amd.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Mismatch between the feature flag name in the commit message title and the actual code.
- [Low] Missing synchronization of `arch/x86/include/asm/cpufeatures.h` with the corresponding tools copy.
--
commit c36f3189418bf1ed5bdfdcfed5326214cecfd96a
Author: Ashish Kalra <ashish.kalra@amd.com>
x86/cpufeatures: Add X86_FEATURE_AMD_RMPOPT feature flag
This commit adds a new feature flag indicating whether the RMPOPT
instruction is supported. It allows RMP checks to be skipped when 1-GB
memory regions are known to contain no SEV-SNP guest memory.
> x86/cpufeatures: Add X86_FEATURE_AMD_RMPOPT feature flag
[Severity: Medium]
The commit message title states it adds the X86_FEATURE_AMD_RMPOPT feature
flag, but the code implementation defines it as X86_FEATURE_RMPOPT (without
the AMD_ prefix). Should the commit title be updated to accurately reflect
the macro name defined in the code?
> diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h
> index 1b4a48bff18f7..14f23d19d8645 100644
> --- a/arch/x86/include/asm/cpufeatures.h
> +++ b/arch/x86/include/asm/cpufeatures.h
> @@ -76,7 +76,7 @@
> #define X86_FEATURE_K8 ( 3*32+ 4) /* Opteron, Athlon64 */
> #define X86_FEATURE_ZEN5 ( 3*32+ 5) /* CPU based on Zen5 microarchitecture */
> #define X86_FEATURE_ZEN6 ( 3*32+ 6) /* CPU based on Zen6 microarchitecture */
> -/* Free ( 3*32+ 7) */
> +#define X86_FEATURE_RMPOPT ( 3*32+ 7) /* Support for AMD RMPOPT instruction */
[Severity: Low]
Does this update need to be mirrored in
tools/arch/x86/include/asm/cpufeatures.h?
Adding a new CPU feature flag to the kernel header without updating the tools
copy typically causes tools like perf and the check-headers.sh script to emit
build warnings about the kernel ABI header differing from the latest version.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1780427587.git.ashish.kalra@amd.com?part=1
next prev parent reply other threads:[~2026-06-02 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 20:00 [PATCH v6 0/6] Add RMPOPT support Ashish Kalra
2026-06-02 20:00 ` [PATCH v6 1/6] x86/cpufeatures: Add X86_FEATURE_AMD_RMPOPT feature flag Ashish Kalra
2026-06-02 20:10 ` sashiko-bot [this message]
2026-06-02 20:01 ` [PATCH v6 2/6] x86/sev: Initialize RMPOPT configuration MSRs Ashish Kalra
2026-06-02 20:36 ` sashiko-bot
2026-06-02 20:01 ` [PATCH v6 3/6] x86/sev: Add support to perform RMP optimizations asynchronously Ashish Kalra
2026-06-02 20:46 ` sashiko-bot
2026-06-02 20:01 ` [PATCH v6 4/6] x86/sev: Add interface to re-enable RMP optimizations Ashish Kalra
2026-06-02 20:54 ` sashiko-bot
2026-06-02 20:02 ` [PATCH v6 5/6] KVM: SEV: Perform RMP optimizations on SNP guest shutdown Ashish Kalra
2026-06-02 20:02 ` [PATCH v6 6/6] x86/sev: Add debugfs support for RMPOPT Ashish Kalra
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=20260602201039.384491F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Ashish.Kalra@amd.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