Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp1583123pxb; Wed, 2 Feb 2022 08:06:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJyPqEg+BRisO8Wa/keW17iJGcGQMYJDP6dTgAwr3I4o6Di3iyOCulTBidYijUebJmiSMCqJ X-Received: by 2002:a63:3302:: with SMTP id z2mr25297174pgz.209.1643817985116; Wed, 02 Feb 2022 08:06:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643817985; cv=none; d=google.com; s=arc-20160816; b=Z4Kpb85FFYZdlWIUhIhComNnCZvxbooSDPni7zSihjFIU8n7MKLm+j6RWbMKntcREn nyv1wX+jct9aCVK8FET+upK/MNafXX6SWX7DQ1OONcX/KVEOdV60T4GzxeIxfr8VCuAQ Ue0Ed3eY5NiBSgS6YKZKI/vKBZH+CEbEgkEJcZ+4kcr95FD9uXyMQCC7swgme1BNWszm pPUw+2DymJx+AgskiGEyFdhqj3rA/WcV4N0txKHyr0QL3qyQfeOqLmArj1UB4bDNyr7F yY4CAW1b76DMHQEGi0ir2JocOWh5qClGN9freBTAmG4i8gpni10KTMgCRkBOQaZPDiqF 48ig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=pZeRfyP/3NDflTT3uYjL7nAay4ukmclUl6g3683qMY8=; b=GAXuhZg4/NIWEmdejdjUYHsjBKuklyxMNb2v61mmTFEiVIa9026boAwrIk3e72R3YT OFEBrF4W0vCeTlmrOcYImzt5DurxmZbfWZd4VB8jmhDRx/sBRqoCijcK8CRysRqmRqQo fmcRuizJuuWr9ewBXsnqxzxQJNG3O3VE9/RyG2z7kxd7ASMVRyNFhu8d8mRsYPRoYjR8 Ek5ZS+eqIczWnAn2qgohBUmkjlrsKy9vn8b05VnWPp4NbjTvo5HmgvG/QolcvWXBR3nz WghdM+Xtau/AZvPUnFJBSsphS0JS2jmmU3Zf4vE8SgGqRWZRmGZqLi12QsO22iDcv8z9 g/mw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gb2Lqtrf; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m14si20330681plx.328.2022.02.02.08.06.12; Wed, 02 Feb 2022 08:06:25 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gb2Lqtrf; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245021AbiBBIiv (ORCPT + 99 others); Wed, 2 Feb 2022 03:38:51 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:48612 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236289AbiBBIit (ORCPT ); Wed, 2 Feb 2022 03:38:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643791123; 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: in-reply-to:in-reply-to:references:references; bh=pZeRfyP/3NDflTT3uYjL7nAay4ukmclUl6g3683qMY8=; b=gb2Lqtrf1/pQkpVvdVN3YA4VajabStcWtjRd82XkTfRPRQpptxqxHM0LetFOqvfdxzrPyR tfYxdjB279ci9d/CB/3M6Z4uNfexoFvbTTOWqU2s+6YJpOMqD6KuJDN6peCR+aXgHDv5Ie KamQ/mOvq/MzRJ3gxusb9L09SOWSADU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-298-pzyL3YZLODSNqGuB5n4qXg-1; Wed, 02 Feb 2022 03:38:38 -0500 X-MC-Unique: pzyL3YZLODSNqGuB5n4qXg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 88C74184608A; Wed, 2 Feb 2022 08:38:35 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.47]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 11B9462D65; Wed, 2 Feb 2022 08:38:25 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 9C9DF1800397; Wed, 2 Feb 2022 09:38:22 +0100 (CET) Date: Wed, 2 Feb 2022 09:38:22 +0100 From: Gerd Hoffmann To: Dov Murik Cc: linux-efi@vger.kernel.org, Borislav Petkov , Ashish Kalra , Brijesh Singh , Tom Lendacky , Ard Biesheuvel , James Morris , "Serge E. Hallyn" , Andi Kleen , Greg KH , Andrew Scull , Dave Hansen , "Dr. David Alan Gilbert" , Lenny Szubowicz , Peter Gonda , James Bottomley , Tobin Feldman-Fitzthum , Jim Cadden , Daniele Buono , linux-coco@lists.linux.dev, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v7 1/5] efi: Save location of EFI confidential computing area Message-ID: <20220202083822.fgyamauzqco374u2@sirius.home.kraxel.org> References: <20220201124413.1093099-1-dovmurik@linux.ibm.com> <20220201124413.1093099-2-dovmurik@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220201124413.1093099-2-dovmurik@linux.ibm.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 01, 2022 at 12:44:09PM +0000, Dov Murik wrote: > Confidential computing (coco) hardware such as AMD SEV (Secure Encrypted > Virtualization) allows a guest owner to inject secrets into the VMs > memory without the host/hypervisor being able to read them. > > Firmware support for secret injection is available in OVMF, which > reserves a memory area for secret injection and includes a pointer to it > the in EFI config table entry LINUX_EFI_COCO_SECRET_TABLE_GUID. > > If EFI exposes such a table entry, uefi_init() will keep a pointer to > the EFI config table entry in efi.coco_secret, so it can be used later > by the kernel (specifically drivers/virt/coco/efi_secret). It will also > appear in the kernel log as "CocoSecret=ADDRESS"; for example: > > [ 0.000000] efi: EFI v2.70 by EDK II > [ 0.000000] efi: CocoSecret=0x7f22e680 SMBIOS=0x7f541000 ACPI=0x7f77e000 ACPI 2.0=0x7f77e014 MEMATTR=0x7ea0c018 > > The new functionality can be enabled with CONFIG_EFI_COCO_SECRET=y. > > Signed-off-by: Dov Murik Reviewed-by: Gerd Hoffmann take care, Gerd