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.web08.5951.1632475466483332901 for ; Fri, 24 Sep 2021 02:24:26 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=KqL0pDSN; 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=1632475465; 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=qs2qn091XdimXckq2/uMkckyiQq+58Qupo5GuGgY2mA=; b=KqL0pDSNptZIaVAWZF6VXu7wsMGwF2z+quh2rW4gst14P7e9OF25Rw/H+R+x2B2A0JvmrX Ytcl4h84L1nsD26KEE9YS/Smn7egGadubULQ/r4zGHTVcOXYggQaVw8w11tMW4zSAYJMC5 amDj9KywK4rR5ILueIfUOCoSDsumlMI= 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-459-Xs7gMYy-PPq7GA5adF1AvA-1; Fri, 24 Sep 2021 05:24:24 -0400 X-MC-Unique: Xs7gMYy-PPq7GA5adF1AvA-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BC2838015C7; Fri, 24 Sep 2021 09:24:22 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.134]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 700AF5D9CA; Fri, 24 Sep 2021 09:24:22 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id A793D180063A; Fri, 24 Sep 2021 11:24:20 +0200 (CEST) Date: Fri, 24 Sep 2021 11:24:20 +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: <20210924092420.a2r6tsiah2bj4zku@sirius.home.kraxel.org> References: <20210923084821.yxizus3loa2p6hms@sirius.home.kraxel.org> <7c9aeb95-5c33-bd8d-4f0c-40133f4c7c3d@amd.com> <20210924053713.fy4ulz3ykbs4xqka@sirius.home.kraxel.org> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 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 Fri, Sep 24, 2021 at 07:36:10AM +0000, Yao, Jiewen wrote: > That is my question. > AMD has its own extension. TDX has its own extension. > Why we have to unify the firmware binary, and to make both us unconfirmable? Isn't that the plan anyway? At least for "config-a" with a basic feature set? See other mail just sent for comments on "config-b". > Or do we want to unify ARM/AARch64/RISC-V ? Not sure what you are trying to tell me. take care, Gerd