From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751409AbdJBNwR (ORCPT ); Mon, 2 Oct 2017 09:52:17 -0400 Received: from mx2.suse.de ([195.135.220.15]:52289 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751128AbdJBNwQ (ORCPT ); Mon, 2 Oct 2017 09:52:16 -0400 Date: Mon, 2 Oct 2017 15:51:51 +0200 From: Borislav Petkov To: Tom Lendacky Cc: Brijesh Singh , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , kvm@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/CPU/AMD, mm: Extend with mem_encrypt=sme option Message-ID: <20171002135151.6y7awrqoc6foa6wf@pd.tnic> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --