From: Dave Hansen <dave.hansen@intel.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: 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: Tue, 31 Jan 2023 14:48:05 -0800 [thread overview]
Message-ID: <16e3217b-1561-51ea-7514-014e27240402@intel.com> (raw)
In-Reply-To: <8b2771ce-9cfa-54cc-de6b-e80ce7af0a93@intel.com>
We've been talking about this inside Intel. Suffice to say that DOITM
was not designed to be turned on all the time. If software turns it on
all the time, it won't accomplish what it was designed to do.
The _most_ likely thing that's going to happen is that DOITM gets
redefined to be much more limited in scope. The current DOITM
architecture is very broad, but the implementations have much more
limited effects. This means that the architecture can probably be
constrained and still match the hardware that's out there today. That's
pure speculation (ha!) on my part.
I think we should hold off on merging any DOITM patches until the dust
settles. As far as I know, there is no pressing practical reason to
apply something urgently.
Any objections?
next prev parent reply other threads:[~2023-01-31 22:48 UTC|newest]
Thread overview: 20+ 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 [this message]
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
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=16e3217b-1561-51ea-7514-014e27240402@intel.com \
--to=dave.hansen@intel.com \
--cc=Jason@zx2c4.com \
--cc=agl@google.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).