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.133.124])
 by mx.groups.io with SMTP id smtpd.web12.6036.1634195321517848973
 for <devel@edk2.groups.io>;
 Thu, 14 Oct 2021 00:08:41 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hG63h3q9;
 spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1634195320;
	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=LbLlvemOviNi2MhVvRM13uMMfXmraHKq8fJSAvt5mpQ=;
	b=hG63h3q9LyFqWzep31JOAdHgOXRKz7OTLnbmqSoE4TxwOiB7KhpTE75iIjTlx7vXm+DPVH
	3wXQ2drwT+Ckmed1wMFVK2Wu3I2GMzrGoG8NRRqDfBfNun/r4i3s8MbS+lXQ37VZYHVgAs
	IAVjgWya+yO3/OXPap8YXuvVzMspG6Y=
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-120-QgLXoYLXP_qnpJUseqWbSA-1; Thu, 14 Oct 2021 03:08:37 -0400
X-MC-Unique: QgLXoYLXP_qnpJUseqWbSA-1
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A996D9F92A;
	Thu, 14 Oct 2021 07:08:35 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.23])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 68A7C5F4F9;
	Thu, 14 Oct 2021 07:08:34 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 0F57818007AC; Thu, 14 Oct 2021 09:08:32 +0200 (CEST)
Date: Thu, 14 Oct 2021 09:08:32 +0200
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: devel@edk2.groups.io, James Bottomley <jejb@linux.ibm.com>,
	Min Xu <min.m.xu@intel.com>, Jiewen Yao <jiewen.yao@intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Erdem Aktas <erdemaktas@google.com>,
	Michael Roth <Michael.Roth@amd.com>
Subject: Re: [PATCH v9 04/32] OvmfPkg/ResetVector: introduce SEV metadata descriptor for VMM use
Message-ID: <20211014070832.sy2ezblvl6olpbtd@sirius.home.kraxel.org>
References: <20211013165713.727815-1-brijesh.singh@amd.com>
 <20211013165713.727815-5-brijesh.singh@amd.com>
MIME-Version: 1.0
In-Reply-To: <20211013165713.727815-5-brijesh.singh@amd.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15
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 Wed, Oct 13, 2021 at 11:56:45AM -0500, Brijesh Singh wrote:
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3275
> 
> The OvmfPkgX86 build reserves memory regions in MEMFD. The memory regions
> get accessed in the SEC phase. AMD SEV-SNP require that the guest's
> private memory be accepted or validated before access.
> 
> Introduce a Guided metadata structure that describes the reserved memory
> regions. The VMM can locate the metadata structure by iterating through
> the reset vector guid and process the areas based on the platform
> specific requirements.

Acked-by: Gerd Hoffmann <kraxel@redhat.com>

(does it make sense to migrate over the existing SEV_FW_HASH_BLOCK_BASE
and SEV_LAUNCH_SECRET_BASE blocks?)

take care,
  Gerd