public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xin Li <xin@zytor.com>
To: Borislav Petkov <bp@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Xin Li <xin3.li@intel.com>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: Re: [PATCH] x86/cpufeatures: Correct LKGS feature flag description
Date: Wed, 15 Oct 2025 23:08:17 +0800	[thread overview]
Message-ID: <2dd4dbee-dc7d-4118-be6d-94bd6d0d5030@zytor.com> (raw)
In-Reply-To: <20251015103548.10194-1-bp@kernel.org>

On 10/15/2025 6:35 PM, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> 
> Quotation marks in cpufeatures.h comments are special and when the
> comment begins with a quoted string, that string lands in /proc/cpuinfo,
> turning it into a user-visible one.
> 
> The LKGS comment doesn't begin with a quoted string but just in case
> drop the quoted "kernel" in there to avoid confusion. And while at it,
> simply change the description into what the LKGS instruction does for
> more clarity.
> 
> No functional changes.
> 
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> ---
>   arch/x86/include/asm/cpufeatures.h       | 2 +-
>   tools/arch/x86/include/asm/cpufeatures.h | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/x86/include/asm/cpufeatures.h b/arch/x86/include/asm/cpufeatures.h
> index 80b68f4726e7..4fb5e12dbdbf 100644
> --- a/arch/x86/include/asm/cpufeatures.h
> +++ b/arch/x86/include/asm/cpufeatures.h
> @@ -320,7 +320,7 @@
>   #define X86_FEATURE_FSRS		(12*32+11) /* Fast short REP STOSB */
>   #define X86_FEATURE_FSRC		(12*32+12) /* Fast short REP {CMPSB,SCASB} */
>   #define X86_FEATURE_FRED		(12*32+17) /* "fred" Flexible Return and Event Delivery */
> -#define X86_FEATURE_LKGS		(12*32+18) /* Load "kernel" (userspace) GS */
> +#define X86_FEATURE_LKGS		(12*32+18) /* MSR_KERNEL_GS_BASE = GS.base */

Yes, the assignment is more clearer to us programmers.

I'm just not sure if "correct" in the shortlog is accurate; it sounds the
existing one is wrong.  Otherwise,

Reviewed-by: Xin Li (Intel) <xin@zytor.com>






>   #define X86_FEATURE_WRMSRNS		(12*32+19) /* Non-serializing WRMSR */
>   #define X86_FEATURE_AMX_FP16		(12*32+21) /* AMX fp16 Support */
>   #define X86_FEATURE_AVX_IFMA            (12*32+23) /* Support for VPMADD52[H,L]UQ */
> diff --git a/tools/arch/x86/include/asm/cpufeatures.h b/tools/arch/x86/include/asm/cpufeatures.h
> index bd655e100395..d5f091babf96 100644
> --- a/tools/arch/x86/include/asm/cpufeatures.h
> +++ b/tools/arch/x86/include/asm/cpufeatures.h
> @@ -320,7 +320,7 @@
>   #define X86_FEATURE_FSRS		(12*32+11) /* Fast short REP STOSB */
>   #define X86_FEATURE_FSRC		(12*32+12) /* Fast short REP {CMPSB,SCASB} */
>   #define X86_FEATURE_FRED		(12*32+17) /* "fred" Flexible Return and Event Delivery */
> -#define X86_FEATURE_LKGS		(12*32+18) /* Load "kernel" (userspace) GS */
> +#define X86_FEATURE_LKGS		(12*32+18) /* MSR_KERNEL_GS_BASE = GS.base */
>   #define X86_FEATURE_WRMSRNS		(12*32+19) /* Non-serializing WRMSR */
>   #define X86_FEATURE_AMX_FP16		(12*32+21) /* AMX fp16 Support */
>   #define X86_FEATURE_AVX_IFMA            (12*32+23) /* Support for VPMADD52[H,L]UQ */


  reply	other threads:[~2025-10-15 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 10:35 [PATCH] x86/cpufeatures: Correct LKGS feature flag description Borislav Petkov
2025-10-15 15:08 ` Xin Li [this message]
2025-10-15 15:18   ` H. Peter Anvin
2025-10-15 15:34     ` Xin Li
2025-10-15 15:36       ` H. Peter Anvin
2025-10-15 15:41         ` Xin Li
2025-10-15 15:44           ` H. Peter Anvin
2025-10-15 15:49             ` Borislav Petkov
2025-10-16  3:12               ` H. Peter Anvin
2025-10-16 12:41                 ` 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=2dd4dbee-dc7d-4118-be6d-94bd6d0d5030@zytor.com \
    --to=xin@zytor.com \
    --cc=bp@alien8.de \
    --cc=bp@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    --cc=xin3.li@intel.com \
    /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