[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9c17975-dea8-4cf9-9b1b-f44fab203ae9@zytor.com>
Date: Tue, 25 Feb 2025 10:37:15 -0800
From: Xin Li <xin@...or.com>
To: Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>
Cc: Nikolay Borisov <nik.borisov@...e.com>, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
dave.hansen@...ux.intel.com, x86@...nel.org, will@...nel.org,
peterz@...radead.org, yury.norov@...il.com, akpm@...ux-foundation.org,
acme@...nel.org, namhyung@...nel.org, brgerst@...il.com,
andrew.cooper3@...rix.com
Subject: Re: [PATCH v5 0/5] x86/cpufeatures: Automatically generate required
and disabled feature masks
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...
Powered by blists - more mailing lists