From: "tip-bot2 for Brendan Jackman" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Brendan Jackman <jackmanb@google.com>,
Ingo Molnar <mingo@kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/cpu] x86/cpu: Log CPU flag cmdline hacks more verbosely
Date: Tue, 04 Mar 2025 10:26:21 -0000 [thread overview]
Message-ID: <174108398196.14745.189474796391905137.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20250303-setcpuid-taint-louder-v1-3-8d255032cb4c@google.com>
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: d0ba9bcf001c7907e4755b0e498f5ff9d1a228ef
Gitweb: https://git.kernel.org/tip/d0ba9bcf001c7907e4755b0e498f5ff9d1a228ef
Author: Brendan Jackman <jackmanb@google.com>
AuthorDate: Mon, 03 Mar 2025 15:45:39
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Tue, 04 Mar 2025 11:15:12 +01:00
x86/cpu: Log CPU flag cmdline hacks more verbosely
Since using these options is very dangerous, make details as visible as
possible:
- Instead of a single message for each of the cmdline options, print a
separate pr_warn() for each individual flag.
- Say explicitly whether the flag is a "feature" or a "bug".
Suggested-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Brendan Jackman <jackmanb@google.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/r/20250303-setcpuid-taint-louder-v1-3-8d255032cb4c@google.com
---
arch/x86/kernel/cpu/common.c | 39 ++++++++++++++++++++---------------
1 file changed, 23 insertions(+), 16 deletions(-)
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index c1ced31..8eba9ca 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -1484,8 +1484,6 @@ static inline bool parse_set_clear_cpuid(char *arg, bool set)
char *opt;
int taint = 0;
- pr_warn("%s CPUID bits:", set ? "Force-enabling" : "Clearing");
-
while (arg) {
bool found __maybe_unused = false;
unsigned int bit;
@@ -1500,16 +1498,19 @@ static inline bool parse_set_clear_cpuid(char *arg, bool set)
if (!kstrtouint(opt, 10, &bit)) {
if (bit < NCAPINTS * 32) {
+ if (set) {
+ pr_warn("setcpuid: force-enabling CPU feature flag:");
+ setup_force_cpu_cap(bit);
+ } else {
+ pr_warn("clearcpuid: force-disabling CPU feature flag:");
+ setup_clear_cpu_cap(bit);
+ }
/* empty-string, i.e., ""-defined feature flags */
if (!x86_cap_flags[bit])
- pr_cont(" %d:%d", bit >> 5, bit & 31);
+ pr_cont(" %d:%d\n", bit >> 5, bit & 31);
else
- pr_cont(" %s", x86_cap_flags[bit]);
+ pr_cont(" %s\n", x86_cap_flags[bit]);
- if (set)
- setup_force_cpu_cap(bit);
- else
- setup_clear_cpu_cap(bit);
taint++;
}
/*
@@ -1521,11 +1522,15 @@ static inline bool parse_set_clear_cpuid(char *arg, bool set)
for (bit = 0; bit < 32 * (NCAPINTS + NBUGINTS); bit++) {
const char *flag;
+ const char *kind;
- if (bit < 32 * NCAPINTS)
+ if (bit < 32 * NCAPINTS) {
flag = x86_cap_flags[bit];
- else
+ kind = "feature";
+ } else {
+ kind = "bug";
flag = x86_bug_flags[bit - (32 * NCAPINTS)];
+ }
if (!flag)
continue;
@@ -1533,22 +1538,24 @@ static inline bool parse_set_clear_cpuid(char *arg, bool set)
if (strcmp(flag, opt))
continue;
- pr_cont(" %s", opt);
- if (set)
+ if (set) {
+ pr_warn("setcpuid: force-enabling CPU %s flag: %s\n",
+ kind, flag);
setup_force_cpu_cap(bit);
- else
+ } else {
+ pr_warn("clearcpuid: force-disabling CPU %s flag: %s\n",
+ kind, flag);
setup_clear_cpu_cap(bit);
+ }
taint++;
found = true;
break;
}
if (!found)
- pr_cont(" (unknown: %s)", opt);
+ pr_warn("%s: unknown CPU flag: %s", set ? "setcpuid" : "clearcpuid", opt);
}
- pr_cont("\n");
-
return taint;
}
next prev parent reply other threads:[~2025-03-04 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 15:45 [PATCH 0/3] x86/cpu: Followups to adding setcpuid= Brendan Jackman
2025-03-03 15:45 ` [PATCH 1/3] x86/cpu: Remove some macros about feature names Brendan Jackman
2025-03-04 8:27 ` [tip: x86/cpu] x86/cpu: Remove unnecessary macro indirection related to CPU " tip-bot2 for Brendan Jackman
2025-03-04 10:26 ` tip-bot2 for Brendan Jackman
2025-03-03 15:45 ` [PATCH 2/3] x86/cpu: Warn louder about {set,clear}cpuid Brendan Jackman
2025-03-04 8:27 ` [tip: x86/cpu] x86/cpu: Warn louder about the {set,clear}cpuid boot parameters tip-bot2 for Brendan Jackman
2025-03-04 10:26 ` tip-bot2 for Brendan Jackman
2025-03-03 15:45 ` [PATCH 3/3] x86/cpu: Log CPU flag cmdline hacks more verbosely Brendan Jackman
2025-03-04 8:27 ` [tip: x86/cpu] " tip-bot2 for Brendan Jackman
2025-03-04 10:26 ` tip-bot2 for Brendan Jackman [this message]
2025-03-03 16:12 ` [PATCH 0/3] x86/cpu: Followups to adding setcpuid= Borislav Petkov
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=174108398196.14745.189474796391905137.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@alien8.de \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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®