From: Xin Li <xin@zytor.com>
To: Nikolay Borisov <nik.borisov@suse.com>,
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
Subject: Re: [PATCH v4 2/4] x86/cpufeatures: Generate a feature mask header based on build config
Date: Wed, 3 Jul 2024 02:23:08 -0700 [thread overview]
Message-ID: <8744fbf0-46b9-4df9-951c-4f1ddafd7b36@zytor.com> (raw)
In-Reply-To: <df5b3001-e79b-4bfd-a2a1-c63111feba8a@suse.com>
On 7/1/2024 3:44 AM, Nikolay Borisov wrote:
>
>
> On 28.06.24 г. 20:45 ч., Xin Li (Intel) wrote:
> Overall it's better I still have some minor comments which can be
> addressed only if you are going to make another submission.
I can send a v4A for this patch.
>
>> diff --git a/arch/x86/tools/featuremasks.awk
>> b/arch/x86/tools/featuremasks.awk
>> new file mode 100755
>> index 000000000000..351d5a4c7d64
>> --- /dev/null
>> +++ b/arch/x86/tools/featuremasks.awk
>> @@ -0,0 +1,85 @@
>> +#!/usr/bin/awk
>> +#
>> +# Convert cpufeatures.h to a list of compile-time masks
>> +# Note: this blithly assumes that each word has at least one
>> +# feature defined in it; if not, something else is wrong!
>> +#
>> +
>> +BEGIN {
>> + printf "#ifndef _ASM_X86_FEATUREMASKS_H\n";
>> + printf "#define _ASM_X86_FEATUREMASKS_H\n\n";
>> +
>> + file = 0
>> +}
>> +
>> +BEGINFILE {
>> + switch (++file) {
>> + case 1: # cpufeatures.h
>> + FPAT = "#[ \t]*[a-z]+|[A-Za-z0-9_]+|[^ \t]";
>> + break;
>> + case 2: # .config
>> + FPAT = "CONFIG_[A-Z0-9_]+|is not set|[yn]";
>> + break;
>> + }
>> +}
>> +
>> +# Create a dictionary of sorts, containing all defined feature bits
>> +file == 1 && $1 ~ /^#[ \t]*define$/ && $2 ~ /^X86_FEATURE_/ &&
>> +$3 == "(" && $5 == "*" && $7 == "+" && $9 == ")" {
>> + nfeat = $4 * $6 + $8;
>> + feat = $2;
>> + sub(/^X86_FEATURE_/, "", feat);
>> + feats[nfeat] = feat;
>> +}
>> +file == 1 && $1 ~ /^#[ \t]*define$/ && $2 == "NCAPINTS" {
>> + ncapints = strtonum($3);
>> +}
>> +
>> +# Create a dictionary featstat[REQUIRED|DISABLED, FEATURE_NAME] = on
>> | off
>> +file == 2 && $1 ~ /^CONFIG_X86_[A-Z]*_FEATURE_/ {
>> + on = ($2 == "y");
>> + if (split($1, fs, "CONFIG_X86_|_FEATURE_") == 3)
>> + featstat[fs[2], fs[3]] = on;
>
> nit: 'on' here will either be 0 or 1 (awk doesn't have a separate
> boolean type).
No change proposed here, right?
>
>> +}
>> +
>> +END {
>> + sets[1] = "REQUIRED";
>> + sets[2] = "DISABLED";
>> +
>> + for (ns in sets) {
>> + s = sets[ns];
> nit: 's' -> 'state', though is 'state' the most appropriate word here?
's' is the tag string, "REQUIRED" or "DISABLED".
>
>> +
>> + printf "/*\n";
>> + printf " * %s features:\n", s;
>> + printf " *\n";
>> + fstr = "";
>> + for (i = 0; i < ncapints; i++) {
>> + mask = 0;
>> + for (j = 0; j < 32; j++) {
>> + nfeat = i*32 + j;
>> + feat = feats[nfeat];
>> + if (feat) {
>> + st = !!featstat[s, feat];
>
> No point in doing the !! dance here, the value written there is already
> true or false since it comes as a result from the earlier check. Just
> drop the !! also what's with the 1 or 2 letter variables. 'st'->
> 'enabled' then the check reads 'if (enabled) { foo }'
Sounds reasonable, I can make the change.
>
>> + if (st) {
>> + nfstr = fstr " " feat;
>> + if (length(nfstr) > 72) {
>> + printf " * %s\n", fstr;
>> + nfstr = " " feat;
>> + }
>> + fstr = nfstr;
>> + mask += (2 ^ j);
>> + }
>> + }
>> + }
>> + masks[i] = mask;
>> + }
>> + printf " * %s\n */\n", fstr;
>> +
>> + for (i = 0; i < ncapints; i++)
>> + printf "#define %s_MASK%d\t0x%08xU\n", s, i, masks[i];
>> +
>> + printf "#define %s_MASK_CHECK BUILD_BUG_ON_ZERO(NCAPINTS !=
>> %d)\n\n", s, ncapints;
>> + }
>> +
>> + printf "#endif /* _ASM_X86_FEATUREMASKS_H */\n";
>> +}
>
next prev parent reply other threads:[~2024-07-03 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 17:45 [PATCH v4 0/4] x86/cpufeatures: Automatically generate required and disabled feature masks 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 [this message]
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 ` [PATCH v4 0/4] x86/cpufeatures: Automatically generate required and disabled feature masks Xin Li
2024-12-04 17:56 ` 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=8744fbf0-46b9-4df9-951c-4f1ddafd7b36@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®