[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16e3217b-1561-51ea-7514-014e27240402@intel.com>
Date: Tue, 31 Jan 2023 14:48:05 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: Jann Horn <jannh@...gle.com>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Roxana Bradescu <roxabee@...omium.org>,
Adam Langley <agl@...gle.com>,
Ard Biesheuvel <ardb@...nel.org>,
"Jason A . Donenfeld" <Jason@...c4.com>
Subject: Re: [PATCH] x86: enable Data Operand Independent Timing Mode
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?
Powered by blists - more mailing lists