From: Xin Li <xin@zytor.com>
To: Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Nikolay Borisov <nik.borisov@suse.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
Subject: Re: [PATCH v5 0/5] x86/cpufeatures: Automatically generate required and disabled feature masks
Date: Tue, 25 Feb 2025 10:37:15 -0800 [thread overview]
Message-ID: <e9c17975-dea8-4cf9-9b1b-f44fab203ae9@zytor.com> (raw)
In-Reply-To: <20250225181551.GDZ74I1we9xqM_oj-b@fat_crate.local>
On 2/25/2025 10:15 AM, Borislav Petkov wrote:
> On Tue, Feb 25, 2025 at 10:10:03AM -0800, H. Peter Anvin wrote:
>> Yeah we had that debate back and forth. Although I personally feel that any
>> sensible build host would have or be able to have Perl, the consensus
>> opinion seems to be that if it can be done with POSIX standard tools or
>> host-side C it should be unless there is a very strong justification to the
>> contrary.
>
> Right, Xin, please make sure you put this rationale in the commit message so
> that people can read it.
Oh, I'm thinking to stick to awk with rewriting the part that a standard
POSIX awk doesn't support...
next prev parent reply other threads:[~2025-02-25 18:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 7:07 Xin Li (Intel)
2025-01-06 7:07 ` [PATCH v5 1/5] x86/cpufeatures: Add {required,disabled} feature configs Xin Li (Intel)
2025-02-14 21:58 ` Borislav Petkov
2025-02-15 10:12 ` H. Peter Anvin
2025-02-15 14:20 ` Borislav Petkov
2025-02-15 14:27 ` H. Peter Anvin
2025-02-15 14:30 ` Borislav Petkov
2025-02-15 14:35 ` H. Peter Anvin
2025-02-15 14:44 ` Borislav Petkov
2025-01-06 7:07 ` [PATCH v5 2/5] x86/cpufeatures: Generate a feature mask header based on build config Xin Li (Intel)
2025-01-06 7:07 ` [PATCH v5 3/5] x86/cpufeatures: Remove {disabled,required}-features.h Xin Li (Intel)
2025-01-06 7:07 ` [PATCH v5 4/5] x86/cpufeatures: Use AWK to generate {REQUIRED|DISABLED}_MASK_BIT_SET Xin Li (Intel)
2025-01-06 7:07 ` [PATCH v5 5/5] x86/cpufeatures: Add the CPU feature bit for MSR immediate form instructions Xin Li (Intel)
2025-02-22 16:30 ` Borislav Petkov
2025-02-22 18:12 ` Borislav Petkov
2025-02-24 7:30 ` Xin Li
2025-02-24 17:27 ` H. Peter Anvin
2025-02-11 2:25 ` [PATCH v5 0/5] x86/cpufeatures: Automatically generate required and disabled feature masks Xin Li
2025-02-23 10:27 ` Borislav Petkov
2025-02-25 17:10 ` Xin Li
2025-02-25 17:49 ` Borislav Petkov
2025-02-25 17:54 ` Nikolay Borisov
2025-02-25 18:00 ` Borislav Petkov
2025-02-25 18:10 ` H. Peter Anvin
2025-02-25 18:15 ` Borislav Petkov
2025-02-25 18:37 ` Xin Li [this message]
2025-02-25 20:30 ` H. Peter Anvin
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=e9c17975-dea8-4cf9-9b1b-f44fab203ae9@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 \
--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®