public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
To: devel@edk2.groups.io
Cc: jiewen.yao@intel.com, min.m.xu@intel.com, kraxel@redhat.com,
	sebastien.boeuf@intel.com
Subject: [PATCH 0/3] OvmfPkg: Make IntelTdx work with Cloud Hypervisor
Date: Mon, 12 Dec 2022 10:03:40 +0100	[thread overview]
Message-ID: <cover.1670835199.git.sebastien.boeuf@intel.com> (raw)

From: Sebastien Boeuf <sebastien.boeuf@intel.com>

The IntelTdxX64 OVMF target wasn't working with Cloud Hypervisor on TDX
platform. This was due to the way the OVMF code expects Cloud Hypervisor
to rely on PVH to retrieve information like memory below 4GiB as well as
the ACPI tables.

This is why this series takes care of identifying when running on TDX in
order to handle things differently. For the memory below 4GiB, it falls
back onto the CMOS to retrieve the correct information, and for the ACPI
tables, it relies on the HOB to obtain every table individually before
to expose them to the guest OS.

With these two use cases properly handled by this series, it is now
possible to use the IntelTdxX64 target to build an OVMF binary that
works both for QEMU and Cloud Hypervisor on a TDX platform.

Sebastien Boeuf (3):
  OvmfPkg/PlatformInitLib: Differentiate TDX case for Cloud Hypervisor
  OvmfPkg/PlatformInitLib: Transfer GUID Extension HOB
  OvmfPkg/AcpiPlatformDxe: Differentiate TDX case for Cloud Hypervisor

 OvmfPkg/AcpiPlatformDxe/AcpiPlatform.c      |  8 +-
 OvmfPkg/AcpiPlatformDxe/AcpiPlatform.h      |  6 ++
 OvmfPkg/AcpiPlatformDxe/AcpiPlatformDxe.inf |  2 +
 OvmfPkg/AcpiPlatformDxe/CloudHvAcpi.c       | 87 +++++++++++++++++++++
 OvmfPkg/Library/PlatformInitLib/IntelTdx.c  |  5 ++
 OvmfPkg/Library/PlatformInitLib/MemDetect.c |  4 +-
 OvmfPkg/OvmfPkg.dec                         |  1 +
 7 files changed, 111 insertions(+), 2 deletions(-)

-- 
2.34.1

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 5 208 026.16 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


             reply	other threads:[~2022-12-12  9:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  9:03 Boeuf, Sebastien [this message]
2022-12-12  9:03 ` [PATCH 1/3] OvmfPkg/PlatformInitLib: Differentiate TDX case for Cloud Hypervisor Boeuf, Sebastien
2022-12-13  0:04   ` Min Xu
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=cover.1670835199.git.sebastien.boeuf@intel.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