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.5555.1634274021507380801
 for <devel@edk2.groups.io>;
 Thu, 14 Oct 2021 22:00:22 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=g6/9Ff7q;
 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=1634274020;
	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=hgJFV0CsjldBvjBD7+sjA3PfgHlMnVbVBalU1sa2ttE=;
	b=g6/9Ff7qUr4Iqb8l2Pj+n0ePL1jTiino7a0KkrjspynM7ZdxHz7jYlHYKgRBjimNivFU63
	0r/lgXXxFJ6tnuNSRAReoVaD4s5gfdDzA0WuFbeUavHyuKOygU7HKpT3XmFYmk0Gd/5DPk
	UJBwdHalatqQHpTIq0GLVIW1Vn9z1bo=
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-31-6rXzmiLbNteSlP5Bgqyusw-1; Fri, 15 Oct 2021 01:00:16 -0400
X-MC-Unique: 6rXzmiLbNteSlP5Bgqyusw-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C0A4F100CCC3;
	Fri, 15 Oct 2021 05:00:14 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.23])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 4613269FA4;
	Fri, 15 Oct 2021 05:00:14 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 3CB9D1800393; Fri, 15 Oct 2021 07:00:08 +0200 (CEST)
Date: Fri, 15 Oct 2021 07:00:08 +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 1/2] Ovmfpkg: update Ia32 build to use new work area
Message-ID: <20211015050008.3tiwnoipzod44rha@sirius.home.kraxel.org>
References: <20211014181711.784074-1-brijesh.singh@amd.com>
 <20211014181711.784074-2-brijesh.singh@amd.com>
MIME-Version: 1.0
In-Reply-To: <20211014181711.784074-2-brijesh.singh@amd.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
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, Oct 14, 2021 at 01:17:10PM -0500, Brijesh Singh wrote:
> The commit 80e67af9afca added support for the generic work area concept
> used mainly by the encrypted VMs. In the past, the work area was
> preliminary used by the SEV-ES VMs. The SEV-ES support is available for
> the X64 builds only. But now, that work area header contains fields that
> nonencrypted VMs and SEV VMs can use. They can be built for IA32. So,
> moving the work area defines outside of X64.

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