Thread (91 messages) 91 messages, 11 authors, 2018-12-13

Re: [RFC v2 00/13] Multi-Key Total Memory Encryption API (MKTME)

From: Kirill A. Shutemov <hidden>
Date: 2018-12-06 11:23:02
Also in: keyrings, linux-mm

On Wed, Dec 05, 2018 at 08:32:52PM +0000, Sakkinen, Jarkko wrote:
On Tue, 2018-12-04 at 12:46 +0300, Kirill A. Shutemov wrote:
quoted
On Tue, Dec 04, 2018 at 09:25:50AM +0000, Peter Zijlstra wrote:
quoted
On Mon, Dec 03, 2018 at 11:39:47PM -0800, Alison Schofield wrote:
quoted
(Multi-Key Total Memory Encryption)
I think that MKTME is a horrible name, and doesn't appear to accurately
describe what it does either. Specifically the 'total' seems out of
place, it doesn't require all memory to be encrypted.
MKTME implies TME. TME is enabled by BIOS and it encrypts all memory with
CPU-generated key. MKTME allows to use other keys or disable encryption
for a page.
When you say "disable encryption to a page" does the encryption get
actually disabled or does the CPU just decrypt it transparently i.e.
what happens physically?
Yes, it gets disabled. Physically. It overrides TME encryption.

-- 
 Kirill A. Shutemov
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help