From: Petr Tesarik <ptesarik@suse.com>
To: Nikolay Borisov <nik.borisov@suse.com>, Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] x86/tsx: Get the tsx= command line parameter with early_param()
Date: Wed, 22 Oct 2025 18:31:04 +0200 [thread overview]
Message-ID: <20251022183040.5b5731cb@mordecai> (raw)
In-Reply-To: <20251008160343.146bd470@mordecai.tesarici.cz>
On Wed, 8 Oct 2025 16:03:43 +0200
Petr Tesarik <ptesarik@suse.com> wrote:
> On Tue, 7 Oct 2025 15:50:02 +0300
> Nikolay Borisov <nik.borisov@suse.com> wrote:
>
> > On 26.09.25 г. 21:01 ч., Petr Tesarik wrote:
> > > Use early_param() to get the value of the tsx= command line parameter.
> > > Although cmdline_find_option() works fine, the option is later reported
> > > as unknown and passed to user space. The latter is not a real issue, but
> > > the former is confusing and makes people wonder if the tsx= parameter had
> > > any effect and double-check for typos unnecessarily.
> > >
> > > The behavior changes slightly if "tsx" is given without any argument (which
> > > is invalid syntax). Prior to this patch, the kernel logged an error message
> > > and disabled TSX. With this patch, the parameter is ignored. The new
> > > behavior is consistent with other parameters, e.g. "tsx_async_abort".
> > >
> > > Signed-off-by: Petr Tesarik <ptesarik@suse.com>
> >
> > LGTM, also could you include some rationale why early_param vs __setup
> > for example, or arch_param_cb (which by the way has yet to find its
> > first user).
>
> I'd love to, but I'm a noob myself, so I simply followed Borislav's
> advice here:
>
> https://lore.kernel.org/all/20250915143909.GAaMglDd5oRSPDDuqu@fat_crate.local/
>
> @Borislav: Would you mind explaining your request to use early_param()?
Never mind, I have spent some time on it, so here's a dump of how I
understand it:
https://sigillatum.tesarici.cz/2025-10-22-kernel-parameters.html
HTH
Petr T
next prev parent reply other threads:[~2025-10-22 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 18:01 [PATCH v2 0/2] x86/tsx: Improve handling of the tsx= kernel parameter Petr Tesarik
2025-09-26 18:01 ` [PATCH v2 1/2] x86/tsx: Make tsx_ctrl_state static Petr Tesarik
2025-10-07 12:40 ` Nikolay Borisov
2025-10-09 17:58 ` Pawan Gupta
2025-09-26 18:01 ` [PATCH v2 2/2] x86/tsx: Get the tsx= command line parameter with early_param() Petr Tesarik
2025-10-07 12:50 ` Nikolay Borisov
2025-10-08 14:03 ` Petr Tesarik
2025-10-22 16:31 ` Petr Tesarik [this message]
2025-10-09 18:51 ` Pawan Gupta
2025-10-10 0:33 ` Pawan Gupta
2025-10-10 7:45 ` Petr Tesarik
2025-10-10 17:52 ` Pawan Gupta
2025-10-10 7:40 ` Petr Tesarik
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=20251022183040.5b5731cb@mordecai \
--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
all inboxes | Powered by JetHome®