From: Nikolay Borisov <nik.borisov@suse.com>
To: Dave Hansen <dave.hansen@intel.com>, x86@kernel.org
Cc: dave.hansen@linux.intel.com, mhocko@suse.de,
asit.k.mallick@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2] x86/tsx: Set default TSX mode to auto
Date: Tue, 9 Dec 2025 09:01:36 +0200 [thread overview]
Message-ID: <989e5135-eb55-443d-a836-273249fc51c6@suse.com> (raw)
In-Reply-To: <b7150721-042d-4750-adfa-a66d8b45f365@intel.com>
On 12.11.25 г. 21:13 ч., Dave Hansen wrote:
> On 11/12/25 11:05, Nikolay Borisov wrote:
>> At SUSE we've been releasing our kernels with TSX enabled for the past 6
>> years and some customers have started to rely on it. Furthermore, the last
>> known vulnerability concerning TSX was TAA (CVE-2019-11135) and a
>> significant amount time has passed since then without anyone reporting any
>> issues. Intel has released numerous processors which do not have the
>> TAA vulnerability (Cooper/Ice Lake, Sapphire/Emerald/Granite Rappids)
>> yet TSX remains being disabled by default.
>>
>> The main aim of this patch is to reduce the divergence between SUSE's
>> configuration and the upstream by switching the default TSX mode to
>> auto. I believe this strikes the right balance between keeping it
>> enabled where appropriate (i.e every machine which doesn't contain the
>> TAA vulnerability) and disabling it preventively.
>
> This seems pretty sane to me. TSX is far less scary than it once was. It
> seemed to be a key part of a bunch of the speculation gadgets at some
> point, but having it off by default doesn't really seem to have slowed
> anyone down.
>
> Plus, this won't even change anyone's builds that has a .config from the
> last 5 years.
>
> Does anyone feel differently?
So at the end of the day what is the status of this, will it get merged?
next prev parent reply other threads:[~2025-12-09 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 19:05 Nikolay Borisov
2025-11-12 19:13 ` Dave Hansen
2025-12-09 7:01 ` Nikolay Borisov [this message]
2026-01-06 17:27 ` [tip: x86/cpu] " tip-bot2 for Nikolay Borisov
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=989e5135-eb55-443d-a836-273249fc51c6@suse.com \
--to=nik.borisov@suse.com \
--cc=asit.k.mallick@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.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®