Skip to contentSkip to conversation

x86/split_lock: Don't warn about unknown parameter

PATCH Superseded Ronan Pigott 2 participants 2 messages Apr 5 x86

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 x86/split_lock: Don't warn about unknown parameter

The split_lock_detect command line parameter is handled in sld_setup shortly after cpu_parse_early_param but still before parse_early_param.

Add a dummy __setup function so that parse_early_param doesn't later complain about the "unknown" parameter split_lock_detect=, and pass it along to init.

---
 arch/x86/kernel/cpu/bus_lock.c | 6 ++++++
 1 file changed, 6 insertions(+)
arch/x86/kernel/cpu/bus_lock.c +6 -0
index fb166662bc0d..c8fec79ed557 100644
@@ -132,6 +132,12 @@ static void __init sld_state_setup(void)
 	sld_state = state;
 }
 
+static __init int setup_split_lock_detect(char *arg)
+{
+	return 1;
+}
+__setup("split_lock_detect=", setup_split_lock_detect);
+
 static void __init __split_lock_setup(void)
 {
 	if (!split_lock_verify_msr(false)) {
Signature · 1 line
2.53.0
maintainer
#1 lore raw
Quoted 2 lines · Ronan Pigott

The split_lock_detect command line parameter is handled in sld_setup shortly after cpu_parse_early_param but still before parse_early_param.

Please end function names with parentheses.

When a function is mentioned in the changelog, either the text body or the subject line, please use the format 'function_name()'. Omitting the brackets after the function name can be ambiguous.

Quoted 3 lines

Add a dummy __setup function so that parse_early_param doesn't later complain about the "unknown" parameter split_lock_detect=, and pass it along to init.

verify_tags: WARNING: Sender [Ronan Pigott <[email protected]>] hasn't signed off on the patch!

Signature · 4 lines
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette