From: Petr Tesarik <ptesarik@suse.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Nikolay Borisov <nik.borisov@suse.com>,
x86@kernel.org (maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)),
linux-kernel@vger.kernel.org (open list:X86 ARCHITECTURE (32-BIT
AND 64-BIT)), Petr Tesarik <ptesarik@suse.com>
Subject: [PATCH v3 0/2] x86/tsx: Improve handling of the tsx= kernel parameter
Date: Wed, 22 Oct 2025 12:26:11 +0200 [thread overview]
Message-ID: <cover.1761127696.git.ptesarik@suse.com> (raw)
Parse the tsx= kernel parameter with early_param(), so it is not
reported as unknown.
As a side note, it was not necessary to defer the handling of
tsx=auto. Contrary to Pawan's claim, cpu_set_bug_bits() is called
from setup_arch() via early_cpu_init() and early_identify_cpu() before
parse_early_param(). But it is a nice cleanup, nevertheless, and I
learned something about parsing the command line. Cf. the NAK here:
https://lore.kernel.org/all/20251009185134.fb4evjrk76rwxv37@desk/
Changes from v2:
* compile-time initialization with the configured default
* defer tsx=auto handling to tsx_init()
* add more detail to the commit message
Changes from v1:
* make tsx_ctrl_state local to tsx.c
* use early_param() instead of core_param()
Petr Tesarik (2):
x86/tsx: Make tsx_ctrl_state static
x86/tsx: Get the tsx= command line parameter with early_param()
arch/x86/kernel/cpu/cpu.h | 9 ------
arch/x86/kernel/cpu/tsx.c | 59 ++++++++++++++++++++++-----------------
2 files changed, 34 insertions(+), 34 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-22 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 10:26 Petr Tesarik [this message]
2025-10-22 10:26 ` [PATCH v3 1/2] x86/tsx: Make tsx_ctrl_state static Petr Tesarik
2025-10-22 10:26 ` [PATCH v3 2/2] x86/tsx: Get the tsx= command line parameter with early_param() Petr Tesarik
2025-10-22 17:46 ` Pawan Gupta
2025-10-23 6:45 ` Petr Tesarik
2025-10-23 16:05 ` Pawan Gupta
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=cover.1761127696.git.ptesarik@suse.com \
--to=ptesarik@suse.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=tglx@linutronix.de \
--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