[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z-5pJ6iat-uptEh9@archie.me>
Date: Thu, 3 Apr 2025 17:55:35 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: "Naveen N Rao (AMD)" <naveen@...nel.org>, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Cc: Borislav Petkov <bp@...en8.de>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Jonathan Corbet <corbet@....net>, x86@...nel.org
Subject: Re: [PATCH] Documentation/x86: Clarify naming of CPU features for
/proc/cpuinfo
On Thu, Apr 03, 2025 at 03:13:08PM +0530, Naveen N Rao (AMD) wrote:
> If the comment on the line for the #define X86_FEATURE_* starts with a
> -double-quote character (""), the string inside the double-quote characters
> -will be the name of the flags. For example, the flag "sse4_1" comes from
> -the comment "sse4_1" following the X86_FEATURE_XMM4_1 definition.
> +double-quote character (""), the string inside the double-quote characters will
"... the quoted string ..."
> +be the name of the flag. For example, the flag "sse4_1" comes from the comment
> +"sse4_1" following the X86_FEATURE_XMM4_1 definition. /proc/cpuinfo is a
> +userspace interface and must remain constant. If, for some reason, the naming
> +of X86_FEATURE_<name> changes, one shall retain the name already used in
> +/proc/cpuinfo.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists