From: "Min Xu" <min.m.xu@intel.com>
To: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
"kraxel@redhat.com" <kraxel@redhat.com>
Subject: Re: [PATCH 1/3] OvmfPkg/PlatformInitLib: Differentiate TDX case for Cloud Hypervisor
Date: Tue, 13 Dec 2022 00:04:28 +0000 [thread overview]
Message-ID: <SJ0PR11MB5069927EDDBD04234DFE7163C5E39@SJ0PR11MB5069.namprd11.prod.outlook.com> (raw)
In-Reply-To: <64b42b8bb9bbbafc6abb99c812baec57f1506990.1670835199.git.sebastien.boeuf@intel.com>
On December 12, 2022 5:04 PM, Boeuf, Sebastien wrote:
> Subject: [PATCH 1/3] OvmfPkg/PlatformInitLib: Differentiate TDX case for
> Cloud Hypervisor
>
> From: Sebastien Boeuf <sebastien.boeuf@intel.com>
>
> Rely on the CcProbe() function to identify when running on TDX. This allows
> the firmware to follow a different codepath for Cloud Hypervisor, which
> means it doesn't rely on PVH to find out about memory below 4GiB.
> instead it falls back onto the CMOS to retrieve that information.
>
> Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
> ---
> OvmfPkg/Library/PlatformInitLib/MemDetect.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/OvmfPkg/Library/PlatformInitLib/MemDetect.c
> b/OvmfPkg/Library/PlatformInitLib/MemDetect.c
> index b8feae4309..afee4b1e72 100644
> --- a/OvmfPkg/Library/PlatformInitLib/MemDetect.c
> +++ b/OvmfPkg/Library/PlatformInitLib/MemDetect.c
> @@ -26,6 +26,7 @@ Module Name:
> // #include <Library/BaseLib.h> #include
> <Library/BaseMemoryLib.h>+#include <Library/CcProbeLib.h> #include
> <Library/DebugLib.h> #include <Library/HardwareInfoLib.h> #include
> <Library/HobLib.h>@@ -312,7 +313,8 @@
> PlatformGetSystemMemorySizeBelow4gb (
> UINT8 Cmos0x34; UINT8 Cmos0x35; - if (PlatformInfoHob-
> >HostBridgeDevId == CLOUDHV_DEVICE_ID) {+ if (PlatformInfoHob-
> >HostBridgeDevId == CLOUDHV_DEVICE_ID &&+ CcProbe () !=
> CcGuestTypeIntelTdx) { // Get the information from PVH memmap
> return (UINT32)GetHighestSystemMemoryAddressFromPvhMemmap
> (TRUE); }--
> 2.34.1
Reviewed-by: Min Xu <min.m.xu@intel.com>
next prev parent reply other threads:[~2022-12-13 0:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 9:03 [PATCH 0/3] OvmfPkg: Make IntelTdx work with Cloud Hypervisor Boeuf, Sebastien
2022-12-12 9:03 ` [PATCH 1/3] OvmfPkg/PlatformInitLib: Differentiate TDX case for " Boeuf, Sebastien
2022-12-13 0:04 ` Min Xu [this message]
2022-12-12 9:03 ` [PATCH 2/3] OvmfPkg/PlatformInitLib: Transfer GUID Extension HOB Boeuf, Sebastien
2022-12-13 0:05 ` Min Xu
2022-12-12 9:03 ` [PATCH 3/3] OvmfPkg/AcpiPlatformDxe: Differentiate TDX case for Cloud Hypervisor Boeuf, Sebastien
2022-12-13 0:05 ` Min Xu
2022-12-14 16:19 ` [PATCH 0/3] OvmfPkg: Make IntelTdx work with " Yao, Jiewen
2022-12-15 2:02 ` Yao, Jiewen
2022-12-15 15:11 ` Boeuf, Sebastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR11MB5069927EDDBD04234DFE7163C5E39@SJ0PR11MB5069.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox