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.web08.12084.1645533431037009605
 for <devel@edk2.groups.io>;
 Tue, 22 Feb 2022 04:37:11 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=FJU2FRbZ;
 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=1645533430;
	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=VD9eSA4qOVsEDBrZf7q4em2/EHNY4G/VnELXDD/N0cU=;
	b=FJU2FRbZsoiRNfRVAhLn7YW3AGT/DrIRpMx/uZ800TkZD6XffCw1VRCaSlAXcC+62zaldP
	StvBY7pEdlfWGtTScLNb/b1RLCXkkPkrLcyVBSlIxMDrzwk9K2T4Oi5rzsALsC1LoCc/py
	wHjjmm4HQ5xZUT/iEf+8SxUkTldcgl4=
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-159-k2Ubrhb-OXGqyt5FsxbztA-1; Tue, 22 Feb 2022 07:37:07 -0500
X-MC-Unique: k2Ubrhb-OXGqyt5FsxbztA-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7286F800425;
	Tue, 22 Feb 2022 12:37:04 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.195.81])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id ADB8B83BEB;
	Tue, 22 Feb 2022 12:37:03 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 01E5D180079D; Tue, 22 Feb 2022 13:37:01 +0100 (CET)
Date: Tue, 22 Feb 2022 13:37:01 +0100
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: gaoliming <gaoliming@byosoft.com.cn>, devel@edk2.groups.io,
	'Jordan Justen' <jordan.l.justen@intel.com>,
	'James Bottomley' <jejb@linux.ibm.com>,
	'Pawel Polawski' <ppolawsk@redhat.com>,
	'Erdem Aktas' <erdemaktas@google.com>,
	'Ard Biesheuvel' <ardb+tianocore@kernel.org>,
	'Tom Lendacky' <thomas.lendacky@amd.com>,
	'Min Xu' <min.m.xu@intel.com>, 'Jiewen Yao' <jiewen.yao@intel.com>
Subject: =?UTF-8?B?UmU6IOWbnuWkjTogW2VkazItZGV2ZWxdIFtQQVRDSCAxLzFdIE92bWZQa2cvQW1kU2V2OiByZXNlcnZlIHNucCBwYWdlcw==?=
Message-ID: <20220222123701.6mzgartcgdfdwhp2@sirius.home.kraxel.org>
References: <20220216070057.1307716-1-kraxel@redhat.com>
 <eab0054d-7cfd-3a72-b397-48f19801c8e9@amd.com>
 <024401d823bd$255a84f0$700f8ed0$@byosoft.com.cn>
 <db889cc2-2a89-ba45-44b9-1d755ae4d729@amd.com>
MIME-Version: 1.0
In-Reply-To: <db889cc2-2a89-ba45-44b9-1d755ae4d729@amd.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
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 Mon, Feb 21, 2022 at 09:07:17AM -0600, Brijesh Singh wrote:
> Hi Liming,
> 
> The said PCD is applicable for the SNP. SNP is supported on x86 64-bit only,
> and most of the development is focused around Qemu/OVMF. In other words, the
> Bhyve, Xen, and CloudHV do not support the SNP yet. We can revisit it when
> those HV starts supporting the SNP.

Is there some #define set when building with support for SEV and/or SNP?
If not, should we add one?

I think it would make sense to just not include the OvmfSevMetadata
table (and other metadata) at all when the build doesn't support it.

take care,
  Gerd