From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124])
 by mx.groups.io with SMTP id smtpd.web11.19437.1680161114257969775
 for <devel@edk2.groups.io>;
 Thu, 30 Mar 2023 00:25:14 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=NtDEz4mY;
 spf=pass (domain: redhat.com, ip: 170.10.129.124, mailfrom: kraxel@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1680161112;
	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=L7OvmU6qWzTAbC9LLjWbeP3QTnFq1CIWZm1y1z9ps90=;
	b=NtDEz4mY/X6dhOuWYO4xMn0vCPIWiKSC398BPYJPR8aWBMu6JSLgNIDNMIcwAkzVWpBpQa
	NKoQaHmXiXnISfCa4zNMrcTYb1lLeNKo9QRNIz8pib1fv5D2D1fnu+PONJ9d/5M2B5JII4
	q7jKz8uACNuHHOxpLJtByb+vKLjPki0=
Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com
 [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-381-00nLQ8iXNvmFTJMrrJlj8Q-1; Thu, 30 Mar 2023 03:25:11 -0400
X-MC-Unique: 00nLQ8iXNvmFTJMrrJlj8Q-1
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D1E0B1C05B03;
	Thu, 30 Mar 2023 07:25:10 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.193.49])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id BC1894020C82;
	Thu, 30 Mar 2023 07:25:09 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 5F59A180061B; Thu, 30 Mar 2023 09:25:08 +0200 (CEST)
Date: Thu, 30 Mar 2023 09:25:08 +0200
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Ni, Ray" <ray.ni@intel.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>, 
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH 0/6] Substract TME-MK KEY_ID_BITS from CPU max PA
Message-ID: <m2maw5ysvyrhdnjs6bfotgloelto5vxxjzyog2tueddmxnyp37@zvtdmc53zq7p>
References: <174E9488256AAAA5.22739@groups.io>
 <17509A92F1FF60E5.28404@groups.io>
 <MN6PR11MB8244731906284880899B05CA8C8E9@MN6PR11MB8244.namprd11.prod.outlook.com>
MIME-Version: 1.0
In-Reply-To: <MN6PR11MB8244731906284880899B05CA8C8E9@MN6PR11MB8244.namprd11.prod.outlook.com>
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Mar 30, 2023 at 02:26:25AM +0000, Ni, Ray wrote:
> Gerd,
> This is needed by Intel platform for TME-MK. Can you help to analyze if it has any impact to OVMF? I assume no.

How does that feature interact with vt and tdx?

take care,
  Gerd