From: Xin Li <xin@zytor.com>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
will@kernel.org, peterz@infradead.org, akpm@linux-foundation.org,
acme@kernel.org, namhyung@kernel.org, brgerst@gmail.com,
andrew.cooper3@citrix.com, nik.borisov@suse.com
Subject: Re: [PATCH v4 0/4] x86/cpufeatures: Automatically generate required and disabled feature masks
Date: Mon, 19 Aug 2024 23:25:17 -0700 [thread overview]
Message-ID: <23b9e88b-9d3b-4c34-a243-232ca2f53527@zytor.com> (raw)
In-Reply-To: <20240628174544.3118826-1-xin@zytor.com>
On 6/28/2024 10:45 AM, Xin Li (Intel) wrote:
> The x86 build process first generates required and disabled feature
> masks based on current build config, and then uses these generated
> masks to compile the source code. When a CPU feature is not enabled
> in a build config, e.g., when CONFIG_X86_FRED=n, its feature disable
> flag, i.e., DISABLE_FRED, needs to be properly defined and added to
> a specific disabled CPU features mask in <asm/disabled-features.h>,
> as the following patch does:
> https://lore.kernel.org/all/20231205105030.8698-8-xin3.li@intel.com/.
> As a result, the FRED feature bit is surely cleared in the generated
> kernel binary when CONFIG_X86_FRED=n.
>
> Recently there is another case to repeat the same exercise for the
> AMD SEV-SNP CPU feature:
> https://lore.kernel.org/all/20240126041126.1927228-2-michael.roth@amd.com/.
> https://lore.kernel.org/all/20240126041126.1927228-23-michael.roth@amd.com/.
>
> It was one thing when there were four of CPU feature masks, but with
> over 20 it is going to cause mistakes, e.g.,
> https://lore.kernel.org/lkml/aaed79d5-d683-d1bc-7ba1-b33c8d6db618@suse.com/.
>
> We want to eliminate the stupidly repeated exercise to manually assign
> features to CPU feature words through introducing an AWK script to
> automatically generate a header with required and disabled CPU feature
> masks based on current build config, and this patch set does that.
>
> Link to v3:
> https://lore.kernel.org/lkml/20240622171435.3725548-1-xin@zytor.com/
>
> Changes since v3:
> * Add a few high-level comments to the AWK script (Nikolay Borisov).
> * Use '1U' instead of '1' in feature mask shifting (Andrew Cooper).
> * Checking NCAPINTS isn't necessary anymore. It was needed when these
> macros had to be manually updated, but now if cpufeatures.h changes
> this header will be regenerated (Brian Gerst).
> * Enforce CPU feature mask values to be unsigned.
>
> Changes since v2:
> * Remove AWK code that generates extra debugging comments (Brian Gerst).
> * Move SSE_MASK to verify_cpu.S, the only place it is used (Brian Gerst).
> * Add a patch to generate macros {REQUIRED|DISABLED}_MASK_BIT_SET in the
> new AWK script (Brian Gerst).
>
> Changes since v1:
> * Keep the X86_{REQUIRED,DISABLED}_FEATURE_ prefixes solely in
> arch/x86/Kconfig.cpufeatures (Borislav Petkov).
> * Explain how config option names X86_{REQUIRED,DISABLED}_FEATURE_<name>
> are formed (Borislav Petkov).
> * Remove code generating unused macros {REQUIRED,DISABLED}_FEATURE(x)
> to tell if a CPU feature, e.g., X86_FEATURE_FRED, is a required or
> disabled feature for this particular compile-time configuration.
>
A gentle ping...
next prev parent reply other threads:[~2024-08-20 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 17:45 Xin Li (Intel)
2024-06-28 17:45 ` [PATCH v4 1/4] x86/cpufeatures: Add {required,disabled} feature configs Xin Li (Intel)
2024-06-28 17:45 ` [PATCH v4 2/4] x86/cpufeatures: Generate a feature mask header based on build config Xin Li (Intel)
2024-07-01 10:44 ` Nikolay Borisov
2024-07-03 9:23 ` Xin Li
2024-07-09 5:42 ` [PATCH v4A " Xin Li (Intel)
2024-06-28 17:45 ` [PATCH v4 3/4] x86/cpufeatures: Remove {disabled,required}-features.h Xin Li (Intel)
2024-07-01 11:57 ` Nikolay Borisov
2024-06-28 17:45 ` [PATCH v4 4/4] x86/cpufeatures: Use AWK to generate {REQUIRED|DISABLED}_MASK_BIT_SET Xin Li (Intel)
2024-07-01 11:56 ` Nikolay Borisov
2024-08-20 6:25 ` Xin Li [this message]
2024-12-04 17:56 ` [PATCH v4 0/4] x86/cpufeatures: Automatically generate required and disabled feature masks Xin Li
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=23b9e88b-9d3b-4c34-a243-232ca2f53527@zytor.com \
--to=xin@zytor.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nik.borisov@suse.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®