diff options
author | 2024-06-20 20:47:46 +0200 | |
---|---|---|
committer | 2024-06-20 21:04:22 +0200 | |
commit | 78ce84b9e0a54a0c91a7449f321c1f852c0cd3fc (patch) | |
tree | 292670d7dde6661b370a9b2af948406142e89901 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | x86/CPU/AMD: Always inline amd_clear_divider() (diff) | |
download | wireguard-linux-78ce84b9e0a54a0c91a7449f321c1f852c0cd3fc.tar.xz wireguard-linux-78ce84b9e0a54a0c91a7449f321c1f852c0cd3fc.zip |
x86/cpufeatures: Flip the /proc/cpuinfo appearance logic
I'm getting tired of telling people to put a magic "" in the
#define X86_FEATURE /* "" ... */
comment to hide the new feature flag from the user-visible
/proc/cpuinfo.
Flip the logic to make it explicit: an explicit "<name>" in the comment
adds the flag to /proc/cpuinfo and otherwise not, by default.
Add the "<name>" of all the existing flags to keep backwards
compatibility with userspace.
There should be no functional changes resulting from this.
Acked-by: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/r/20240618113840.24163-1-bp@kernel.org
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions