Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753392AbcD0PaU (ORCPT ); Wed, 27 Apr 2016 11:30:20 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:46183 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752458AbcD0PaO (ORCPT ); Wed, 27 Apr 2016 11:30:14 -0400 Date: Wed, 27 Apr 2016 17:30:10 +0200 From: Pavel Machek To: Tom Lendacky Cc: linux-arch@vger.kernel.org, linux-efi@vger.kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-mm@kvack.org, iommu@lists.linux-foundation.org, Radim =?utf-8?B?S3LEjW3DocWZ?= , Arnd Bergmann , Jonathan Corbet , Matt Fleming , Joerg Roedel , Konrad Rzeszutek Wilk , Paolo Bonzini , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Andrey Ryabinin , Alexander Potapenko , Thomas Gleixner , Dmitry Vyukov Subject: Re: [RFC PATCH v1 02/18] x86: Secure Memory Encryption (SME) build enablement Message-ID: <20160427153010.GA7861@amd> References: <20160426225553.13567.19459.stgit@tlendack-t1.amdoffice.net> <20160426225614.13567.47487.stgit@tlendack-t1.amdoffice.net> <20160322130150.GB16528@xo-6d-61-c0.localdomain> <5720D810.9060602@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5720D810.9060602@amd.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1214 Lines: 33 On Wed 2016-04-27 10:17:36, Tom Lendacky wrote: > On 03/22/2016 08:01 AM, Pavel Machek wrote: > > On Tue 2016-04-26 17:56:14, Tom Lendacky wrote: > >> Provide the Kconfig support to build the SME support in the kernel. > > > > > > Probably should go last in the series? > > Yeah, I've seen arguments both ways for this. Doing it early > allows compiling and testing with it enabled and doing it late > doesn't enable anything until it's all there. I just chose the > former. Doing it early will break bisect, right? Pavel > >> +config AMD_MEM_ENCRYPT > >> + bool "Secure Memory Encryption support for AMD" > >> + depends on X86_64 && CPU_SUP_AMD > >> + ---help--- > >> + Say yes to enable the encryption of system memory. This requires > >> + an AMD processor that supports Secure Memory Encryption (SME). > >> + The encryption of system memory is disabled by default but can be > >> + enabled with the mem_encrypt=on command line option. > >> + > >> # Common NUMA Features > >> config NUMA > >> bool "Numa Memory Allocation and Scheduler Support" > > -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html