From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mx.groups.io with SMTP id smtpd.web12.4376.1632461840538610526 for ; Thu, 23 Sep 2021 22:37:21 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Z5vUgdk0; spf=pass (domain: redhat.com, ip: 216.205.24.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1632461839; 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=etrGgw3YdkCgsUI5t4yS65lg9EGnMFFdzssRBnyaXZ8=; b=Z5vUgdk0v6J/mhNxSs9ZgJ3hKel24J5+JcUUqNzlhzHgF24BgNsWShgNt7C9AcI5u3Xpl9 1AWCLt1KgSiI3Bi2yRALeyUHAZIuU/5z8EwAjz2s8VYc1cTEUQEZaUn9OmCL5UeJxNHbID pC7zg/JDmmeEqhuuJtVjsJkX+uu9nYM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-591-UMq8hNvlPZubKeVtm2Q8tA-1; Fri, 24 Sep 2021 01:37:17 -0400 X-MC-Unique: UMq8hNvlPZubKeVtm2Q8tA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 166B81006AA4; Fri, 24 Sep 2021 05:37:16 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.134]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AB2EB5FC25; Fri, 24 Sep 2021 05:37:15 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id EE7071800840; Fri, 24 Sep 2021 07:37:13 +0200 (CEST) Date: Fri, 24 Sep 2021 07:37:13 +0200 From: "Gerd Hoffmann" To: "Yao, Jiewen" Cc: "Xu, Min M" , Brijesh Singh , "devel@edk2.groups.io" , Ard Biesheuvel , "Justen, Jordan L" , Erdem Aktas , James Bottomley , Tom Lendacky Subject: Re: [edk2-devel] [PATCH V7 1/1] OvmfPkg: Enable TDX in ResetVector Message-ID: <20210924053713.fy4ulz3ykbs4xqka@sirius.home.kraxel.org> References: <20210922074929.e5iwf24t6wyndgbu@sirius.home.kraxel.org> <20210923084821.yxizus3loa2p6hms@sirius.home.kraxel.org> <7c9aeb95-5c33-bd8d-4f0c-40133f4c7c3d@amd.com> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Sep 23, 2021 at 02:19:17PM +0000, Yao, Jiewen wrote: > All fields in TDX metadata are required. So the current SEV proposal > (3 fields) does not work for TDX. The extra fields are used to guide > VMM on how to copy the binary, allocate memory, --verbose please. The VMM loads the firmware just fine today without that metadata because it's defined by the x86 architecture how to the firmware must be loaded. And note that we are discussing an unified normal/sev/tdx firmware binary here, so the "we might do something completely different for tdx in the future" argument isn't very convincing here. take care, Gerd