Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp4104241img; Tue, 26 Mar 2019 03:07:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqwVp31vd0e1CS08lnpn4hWqb6+r+aY7v05g5u4ibq224a/uyRmxhRu0T1AhMjt0ogjZDkfs X-Received: by 2002:a17:902:1008:: with SMTP id b8mr29381287pla.120.1553594859357; Tue, 26 Mar 2019 03:07:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553594859; cv=none; d=google.com; s=arc-20160816; b=TtVYixfd/7ofBvRWevwmLV3qFR1GsOcWhetH/QM5Yv1C1EzVRQly0wmlG1qv4RwOZC UJColOu3qZZdj46xu6zVs8FX2rhDbhq05Zu/a9J5Cx2MXfXtYjuAzDJoWXTo0k4dxanJ 8XZ1b3mKNuUHoR94dZXeolBIoO1IqOmqSWH3Ww64TDuEQpjjtbSZceGTTqNBQk/yq+ag 1IdCOm5WSn+eFbydbJZCFB0MBWItmxI493fp9fa619YvtSiBOUb45e/kciNHiD0FMeRA sm0446aD6diF6s3Hji8mWJfPGr1RlbyEbMDSrivp+xa/xvcUejX6IU2XjMnylIcGuSgn KzBA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:cc:to:subject :content-transfer-encoding:mime-version:references:in-reply-to :user-agent:date:dkim-signature; bh=i6kxqdFfs/VvAWkFucYDxHQbKc7utkP+G1OcERASYhQ=; b=Yj9fiSAQ9dupnA7TCMFdxc3BsSXQKSG27ero4BBv7SZBJwoVMDT39mwgPqIR4NFxxn dBThodB0Ji+e1xfvMiZcnNzrG2xtcm/6vB8UfsZ8SPrfFMkzmxmF9l+cc6LcLl2kn1h1 yGhfQ+GwIsxvjohIlm5GZMjraWALBovkDHQ0SoV3LEIq2khnYMlvbM6/3eS0O3IrM22L XRw9bbMoCDQFAvQ0TKPftzGJzWFyT0Ti8wuCIVP5bFBx+romxtqubwHJi4gOhpbpBwoH vPAItJ5F4Y3M7viC736LvnbSIveamKfLuRO8MXTV7eZ1b229UI8hXgxZcn+xHaoh5ncz yTzw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@alien8.de header.s=dkim header.b=rgIMkKTI; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alien8.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o6si3773642plh.186.2019.03.26.03.07.24; Tue, 26 Mar 2019 03:07:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@alien8.de header.s=dkim header.b=rgIMkKTI; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726553AbfCZKGT (ORCPT + 99 others); Tue, 26 Mar 2019 06:06:19 -0400 Received: from mail.skyhub.de ([5.9.137.197]:42110 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726175AbfCZKGS (ORCPT ); Tue, 26 Mar 2019 06:06:18 -0400 Received: from [10.189.135.50] (x59cc8b32.dyn.telefonica.de [89.204.139.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id BF9D91EC082D; Tue, 26 Mar 2019 11:06:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1553594777; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=i6kxqdFfs/VvAWkFucYDxHQbKc7utkP+G1OcERASYhQ=; b=rgIMkKTI0H2CZdpFTaDwtciENyk97F8j2gYHd48dPWEASvwrILtlnC4SRg1OhVTFlLMYf4 mZL+AFBab98wAkvyjkaBGD0DPgxUvXnNY8YKBqlex6uozCJdYBSYz6J2n9ZJm6E6CIsvXi yFJT0T+lkT2gECQy23Rmi9E93j7KRig= Date: Tue, 26 Mar 2019 11:06:13 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: <20190315103203.13128-1-lijiang@redhat.com> <20190315103203.13128-2-lijiang@redhat.com> <20190324150034.GH23289@zn.tnic> <7b115829-40d9-e55e-dee3-ec8e4766971f@redhat.com> <20190325063742.GA12016@zn.tnic> <652b9166-f06e-c210-3c3f-c9e80a97db18@amd.com> <20190325173239.GO12016@zn.tnic> <11013ad2-2eab-5a7a-d4e2-a9da4920cfab@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH 1/3] kexec: Do not map the kexec area as decrypted when SEV is active To: "Lendacky, Thomas" , "Singh, Brijesh" CC: lijiang , "linux-kernel@vger.kernel.org" , "kexec@lists.infradead.org" , "tglx@linutronix.de" , "mingo@redhat.com" , "x86@kernel.org" , "hpa@zytor.com" , "akpm@linux-foundation.org" , "dyoung@redhat.com" , "bhe@redhat.com" From: Boris Petkov Message-ID: <24AEA0F0-8BDA-4C96-9AC2-F12A7A06C76D@alien8.de> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On March 25, 2019 8:59:28 PM GMT+01:00, "Lendacky, Thomas" wrote: >Maybe what would help is to describe why there is a difference between >SME >and SEV in regards to kexec=2E During a traditional boot under SME, SME >will >encrypt the kernel, so the SME kexec kernel also needs to be >un-encrypted >in order to replicate a normal SME boot=2E During a traditional boot >under >SEV, the kernel has already been loaded encrypted, so the SEV kexec >kernel >needs to be encrypted in order to replicate a normal SEV boot=2E Yah, that should be in a comment above that function=2E Thx=2E --=20 Sent from a small device: formatting sux and brevity is inevitable=2E