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.web11.6260.1634195731266155688
 for <devel@edk2.groups.io>;
 Thu, 14 Oct 2021 00:15:31 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Okpjd3hP;
 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=1634195730;
	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=Tn6JtvdjzRixWEpR4mVK6Y21M0CrbOUtxP8XSFbhRd0=;
	b=Okpjd3hP/p8fqTgDfghlRPDrsWYNT8p6Q9ua6LKQ/vjcSYLnIC55reDz2/2kkBChdW+Z1+
	erBT2HOATGe1rW9xpuDxZjAMaxrj/usAEMvgrOxbz5DerB3jCjQHp0xyIeX/x2+r7mUOPd
	vjHfjSqAsvG2bD4anSdKltZW1W0G+wQ=
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-592-OIimrOHJPkOKIU7A7LFAcg-1; Thu, 14 Oct 2021 03:15:27 -0400
X-MC-Unique: OIimrOHJPkOKIU7A7LFAcg-1
Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C4C731927801;
	Thu, 14 Oct 2021 07:15:25 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.23])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 0EE3F19D9F;
	Thu, 14 Oct 2021 07:15:24 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id B1A2F18007AC; Thu, 14 Oct 2021 09:15:16 +0200 (CEST)
Date: Thu, 14 Oct 2021 09:15:16 +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 08/32] OvmfPkg/ResetVector: use SEV-SNP-validated CPUID values
Message-ID: <20211014071516.lkiymow6v3wej3pl@sirius.home.kraxel.org>
References: <20211013165713.727815-1-brijesh.singh@amd.com>
 <20211013165713.727815-9-brijesh.singh@amd.com>
MIME-Version: 1.0
In-Reply-To: <20211013165713.727815-9-brijesh.singh@amd.com>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23
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:49AM -0500, Brijesh Singh wrote:
> From: Michael Roth <michael.roth@amd.com>
> 
> CPUID instructions are issued during early boot to do things like probe
> for SEV support. Currently these are handled by a minimal #VC handler
> that uses the MSR-based GHCB protocol to fetch the CPUID values from
> the hypervisor. When SEV-SNP is enabled, use the firmware-validated
> CPUID values from the CPUID page instead [1].

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