From: Xin Li <xin@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Aithal, Srikanth" <sraithal@amd.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, will@kernel.org,
peterz@infradead.org, yury.norov@gmail.com,
akpm@linux-foundation.org, acme@kernel.org, namhyung@kernel.org,
brgerst@gmail.com, andrew.cooper3@citrix.com,
nik.borisov@suse.com
Subject: Re: [PATCH v6 3/5] x86/cpufeatures: Generate a feature mask header based on build config
Date: Tue, 4 Mar 2025 23:30:43 -0800 [thread overview]
Message-ID: <81677e85-ff7f-4986-8e0a-6bf54a63ba49@zytor.com> (raw)
In-Reply-To: <20250304102910.GAZ8bV9hXqVb5tA9rs@fat_crate.local>
On 3/4/2025 2:29 AM, Borislav Petkov wrote:
> On Tue, Mar 04, 2025 at 02:18:51AM -0800, Xin Li wrote:
>> It seems that 'archprepare' works, however I'm not sure if it's the best
>> choice. Any suggestion?
>
> Why do you even need featuremasks_hdr as a prereq?
I'm not sure I'm calling it a prereq; it needs to be generated after we
have a build config and before any kernel source file is built.
"perpare" is defined as a post config build target used before starting
building the kernel or the modules, and "archprepare" is used in arch
Makefiles. E.g., on x86, "archprepare" is already used for ORC header
generation:
ifdef CONFIG_UNWINDER_ORC
orc_hash_h := arch/$(SRCARCH)/include/generated/asm/orc_hash.h
orc_hash_sh := $(srctree)/scripts/orc_hash.sh
targets += $(orc_hash_h)
quiet_cmd_orc_hash = GEN $@
cmd_orc_hash = mkdir -p $(dir $@); \
$(CONFIG_SHELL) $(orc_hash_sh) < $< > $@
$(orc_hash_h): $(srctree)/arch/x86/include/asm/orc_types.h
$(orc_hash_sh) FORCE
$(call if_changed,orc_hash)
archprepare: $(orc_hash_h)
endif
>
> In any case, you'd have to redo your patches - we've zapped them from tip.
Sorry for the build noise. Ofc they should be zapped.
BTW, I'm asking if this build check could be added to Intel-LKP.
>
>> Want me to add it btw?
>
> Yes pls.
Sure.
However it needs to change Makefile in the root directory, which is not
maintained in tip, so I will send a separate patch to KERNEL BUILD
maintainers and list. Make sense?
Thanks!
Xin
next prev parent reply other threads:[~2025-03-05 7:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 8:23 [PATCH v6 0/5] x86/cpufeatures: Automatically generate required and disabled feature masks Xin Li (Intel)
2025-02-28 8:23 ` [PATCH v6 1/5] x86/cpufeatures: Rename X86_CMPXCHG64 to X86_CX8 Xin Li (Intel)
2025-02-28 16:53 ` [tip: x86/cpu] " tip-bot2 for H. Peter Anvin (Intel)
2025-02-28 8:23 ` [PATCH v6 2/5] x86/cpufeatures: Add {required,disabled} feature configs Xin Li (Intel)
2025-02-28 16:53 ` [tip: x86/cpu] " tip-bot2 for H. Peter Anvin (Intel)
2025-03-10 8:18 ` [tip: x86/cpu] x86/cpufeatures: Add {REQUIRED,DISABLED} " tip-bot2 for H. Peter Anvin (Intel)
2025-03-10 14:43 ` H. Peter Anvin
2025-03-10 15:06 ` Borislav Petkov
2025-03-10 18:57 ` Ingo Molnar
2025-03-19 11:04 ` [tip: x86/core] " tip-bot2 for H. Peter Anvin (Intel)
2025-02-28 8:23 ` [PATCH v6 3/5] x86/cpufeatures: Generate a feature mask header based on build config Xin Li (Intel)
2025-02-28 16:53 ` [tip: x86/cpu] " tip-bot2 for H. Peter Anvin (Intel)
2025-03-03 11:38 ` [PATCH v6 3/5] " Aithal, Srikanth
2025-03-03 12:05 ` H. Peter Anvin
2025-03-03 13:25 ` Borislav Petkov
2025-03-03 22:34 ` H. Peter Anvin
2025-03-04 10:18 ` Xin Li
2025-03-04 10:29 ` Borislav Petkov
2025-03-05 7:30 ` Xin Li [this message]
2025-03-05 22:04 ` Borislav Petkov
2025-03-22 19:58 ` Xin Li
2025-02-28 8:23 ` [PATCH v6 4/5] x86/cpufeatures: Remove {disabled,required}-features.h Xin Li (Intel)
2025-02-28 16:53 ` [tip: x86/cpu] " tip-bot2 for Xin Li (Intel)
2025-02-28 8:23 ` [PATCH v6 5/5] x86/cpufeatures: Use AWK to generate {REQUIRED|DISABLED}_MASK_BIT_SET Xin Li (Intel)
2025-02-28 16:53 ` [tip: x86/cpu] " tip-bot2 for Xin Li (Intel)
2025-03-10 8:18 ` [tip: x86/cpu] x86/cpufeatures: Use AWK to generate {REQUIRED|DISABLED}_MASK_BIT_SET in <asm/cpufeaturemasks.h> tip-bot2 for Xin Li (Intel)
2025-03-19 11:03 ` [tip: x86/core] " tip-bot2 for Xin Li (Intel)
2025-02-28 9:26 ` [PATCH v6 0/5] x86/cpufeatures: Automatically generate required and disabled feature masks Ingo Molnar
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=81677e85-ff7f-4986-8e0a-6bf54a63ba49@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=sraithal@amd.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=yury.norov@gmail.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
all inboxes | Powered by JetHome®