From: Eric Biggers <ebiggers@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Marvin Häuser" <haeuser@rptu.de>, "Jann Horn" <jannh@google.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
"Peter Zijlstra" <peterz@infradead.org>,
"Roxana Bradescu" <roxabee@chromium.org>,
"Adam Langley" <agl@google.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>
Subject: Re: [PATCH] x86: enable Data Operand Independent Timing Mode
Date: Wed, 18 Mar 2026 09:15:58 -0700 [thread overview]
Message-ID: <20260318161558.GA2255@sol> (raw)
In-Reply-To: <7dfb5fe7-295f-4a29-a633-c2907a1fdb60@intel.com>
On Wed, Mar 18, 2026 at 08:44:05AM -0700, Dave Hansen wrote:
> On 3/18/26 08:33, Marvin Häuser wrote:
> > As I haven’t found any news on the list or the tree, I'd like to
> > inquire whether there’s been any updates on the situation.
>
> I'd summarize it like this: lots of meetings, no updates.
>
> IMNHO (and not speaking for my employer) DOITM itself is dead. There's
> almost no chance of Linux ever doing anything with the existing, public
> DOITM architecture.
Doesn't DOITM still need to be enabled by default for now, given that
data-dependent timing is a backwards compatibility break and code hasn't
been updated to account for it yet?
- Eric
next prev parent reply other threads:[~2026-03-18 16:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 1:28 [PATCH] x86: enable Data Operand Independent Timing Mode Eric Biggers
2023-01-25 3:07 ` Bagas Sanjaya
2023-01-25 15:29 ` Dave Hansen
2023-01-25 16:15 ` Dave Hansen
2023-01-25 16:22 ` Ard Biesheuvel
2023-01-25 16:45 ` Dave Hansen
2023-01-26 10:20 ` Ard Biesheuvel
2023-01-26 13:52 ` Jann Horn
2023-01-26 16:40 ` Dave Hansen
2023-01-26 17:52 ` Jann Horn
2023-01-26 19:12 ` Dave Hansen
2023-01-26 22:37 ` Eric Biggers
2023-01-26 23:58 ` Dave Hansen
2023-01-31 22:48 ` Dave Hansen
2023-02-01 6:54 ` Eric Biggers
2023-02-01 18:09 ` Dave Hansen
2023-02-01 22:33 ` Josh Triplett
2023-02-03 16:25 ` Dave Hansen
2026-03-18 15:33 ` Marvin Häuser
2026-03-18 15:44 ` Dave Hansen
2026-03-18 16:15 ` Eric Biggers [this message]
2026-03-18 16:23 ` Dave Hansen
[not found] ` <D5B3C493-BADA-4906-BB34-E5D60182F611@rptu.de>
2026-03-18 20:16 ` Marvin Häuser
2023-02-03 18:25 ` Dave Hansen
2023-03-03 3:32 ` Roxana Bradescu
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=20260318161558.GA2255@sol \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=agl@google.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=haeuser@rptu.de \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=roxabee@chromium.org \
--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