Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1391575

RE: [RFC PATCH v1 00/18] x86: Secure Memory Encryption (AMD)

Path csiph.com!aioe.org!gothmog.csi.it!bofh.it!news.nic.it!robomod
From "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>
Newsgroups linux.kernel
Subject RE: [RFC PATCH v1 00/18] x86: Secure Memory Encryption (AMD)
Date Sat, 30 Apr 2016 08:20:01 +0200
Message-ID <rtwpX-2ZP-3@gated-at.bofh.it> (permalink)
References <rsx4K-1jL-37@gated-at.bofh.it>
Thread-Topic [RFC PATCH v1 00/18] x86: Secure Memory Encryption (AMD)
Thread-Index AQHRoA7akq/dosLVYUagaO4x9OsVKJ+iC7dA
Accept-Language en-US
Content-Language en-US
X-Originating-IP [16.216.65.182]
Content-Type text/plain; charset="utf-8"
Content-Transfer-Encoding base64
MIME-Version 1.0
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 26
Organization linux.* mail to news gateway
X-Original-Cc Radim Krčmář <rkrcmar@redhat.com>, Arnd Bergmann <arnd@arndb.de>, Jonathan Corbet <corbet@lwn.net>, Matt Fleming <matt@codeblueprint.co.uk>, Joerg Roedel <joro@8bytes.org>, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>, Paolo Bonzini <pbonzini@redhat.com>, Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>, Andrey Ryabinin <aryabinin@virtuozzo.com>, Alexander Potapenko <glider@google.com>, "Thomas Gleixner" <tglx@linutronix.de>, Dmitry Vyukov <dvyukov@google.com>
X-Original-Date Sat, 30 Apr 2016 06:13:33 +0000
X-Original-Message-ID <94D0CD8314A33A4D9D801C0FE68B402963918FDA@G4W3296.americas.hpqcorp.net>
X-Original-References <20160426225553.13567.19459.stgit@tlendack-t1.amdoffice.net>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1391575

Show key headers only | View raw


> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of Tom Lendacky
> Sent: Tuesday, April 26, 2016 5:56 PM
> Subject: [RFC PATCH v1 00/18] x86: Secure Memory Encryption (AMD)
> 
> This RFC patch series provides support for AMD's new Secure Memory
> Encryption (SME) feature.
> 
> SME can be used to mark individual pages of memory as encrypted through the
> page tables. A page of memory that is marked encrypted will be automatically
> decrypted when read from DRAM and will be automatically encrypted when
> written to DRAM. Details on SME can found in the links below.
> 
...
> ...  Certain data must be accounted for
> as having been placed in memory before SME was enabled (EFI, initrd, etc.)
> and accessed accordingly.
> 
...
>       x86/efi: Access EFI related tables in the clear
>       x86: Access device tree in the clear
>       x86: Do not specify encrypted memory for VGA mapping

If the SME encryption key "is created randomly each time a system is booted,"
data on NVDIMMs won't decrypt properly on the next boot.  You need to exclude
persistent memory regions (reported in the UEFI memory map as 
EfiReservedMemoryType with the NV attribute, or as EfiPersistentMemory).

Perhaps the SEV feature will allow key export/import that could work for
NVDIMMs.

---
Robert Elliott, HPE Persistent Memory


Back to linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

RE: [RFC PATCH v1 00/18] x86: Secure Memory Encryption (AMD) "Elliott, Robert (Persistent Memory)" <elliott@hpe.com> - 2016-04-30 08:20 +0200

csiph-web