[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A8B4322F-F298-406F-8F84-9151FD3CEA5F@zytor.com>
Date: Tue, 25 Feb 2025 10:10:03 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Borislav Petkov <bp@...en8.de>, Nikolay Borisov <nik.borisov@...e.com>
CC: Xin Li <xin@...or.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 February 25, 2025 10:00:51 AM PST, Borislav Petkov <bp@...en8.de> wrote:
>On Tue, Feb 25, 2025 at 07:54:50PM +0200, Nikolay Borisov wrote:
>> But don't we use perl even now:
>>
>> $ find . -iname *.pl | wc -l
>> 55
>
>You're searching wrong:
>
>$ git grep -w perl arch/x86/
>arch/x86/crypto/poly1305-x86_64-cryptogams.pl:1:#!/usr/bin/env perl
>$
>
>That's some crypto-special thing.
>
>This'll force it on *everything*.
>
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.
I guess at some point that will add host-side Rust, which will be fun since that adds the whole Rust user space runtime.
Powered by blists - more mailing lists