From: Tom Lendacky Subject: Re: [PATCH] x86/CPU/AMD, mm: Extend with mem_encrypt=sme option Date: Mon, 2 Oct 2017 11:35:47 -0500 Message-ID: <9374e410-4357-840d-7b1d-40bd27cd78a6@amd.com> References: <20170928090242.ber7gynwaldinafa@pd.tnic> <20170929230652.37821-1-brijesh.singh@amd.com> <20170930115604.w4g3oplmyo5oyjeq@pd.tnic> <26bdd83f-f4a0-dbfc-e6f9-fc3780ce0080@amd.com> <20170930214124.74w44yel3gijwlxj@pd.tnic> <6f50eb4c-f2bb-f125-196f-c1456dd6c601@amd.com> <20171001171617.uzwfzps7sxowfram@pd.tnic> <20171002135151.6y7awrqoc6foa6wf@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Brijesh Singh , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , kvm@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org To: Borislav Petkov Return-path: In-Reply-To: <20171002135151.6y7awrqoc6foa6wf@pd.tnic> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 10/2/2017 8:51 AM, Borislav Petkov wrote: > On Mon, Oct 02, 2017 at 08:44:21AM -0500, Tom Lendacky wrote: >> I think we're talking about the same thing. You want sev_enabled to >> indicate whether you can launch an SEV guest. We would still need an >> sev_active variable to distinguish between SME and SEV during kernel >> execution when the sme_me_mask is non-zero. Currently, the SEV feature >> bit acts as "sev_enabled" and the sev_enabled variable acts as >> "sev_active" in this scenario. > > See my last email about sev_host_enabled. Does that sound better? Hmmm... strange, I haven't received that email or that part of the thread for that matter - including Brijesh's reply. I'll talk with Brijesh and let him run with it. Thanks, Tom >