From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, sebastien.boeuf@intel.com
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] [PATCH 2/3] OvmfPkg: CloudHv: Retrieve RSDP address from PVH
Date: Fri, 25 Feb 2022 10:34:05 +0100 [thread overview]
Message-ID: <20220225093405.2rwmieyt4ue3ytg2@sirius.home.kraxel.org> (raw)
In-Reply-To: <dd2425171254622d4d5de3d87fcb1bf332e33bc5.camel@intel.com>
Hi,
> > I'm wondering whenever there are plans for cloudhv to also support
> > sev
> > and/or tdx some day. If so, then it probably isn't a good idea to
> > switch to the xen reset vector.
>
> Well Cloud Hypervisor aims at supporting TDX, but based on a separate
> firmware. We're not trying to support both TDX and non-TDX use cases
> with the same binary, which simplifies the problem here.
If tdx will be another binary anyway then it doesn't matter much I guess.
> > There is the work area used for by
> > confidential computing code, I think it would be an option to store a
> > pointer to the pvh_start_info there.
>
> Sorry I'm not aware of the confidential computing code. Can you point
> me to it?
OvmfPkg/Include/WorkArea.h
git grep WORK_AREA -- OvmfPkg/ResetVector
take care,
Gerd
next prev parent reply other threads:[~2022-02-25 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1645542995.git.sebastien.boeuf@intel.com>
2022-02-22 15:53 ` [PATCH 1/3] OvmfPkg: Generate CloudHv as a PVH ELF binary Boeuf, Sebastien
2022-02-23 11:22 ` [edk2-devel] " Gerd Hoffmann
2022-02-23 12:35 ` Boeuf, Sebastien
2022-02-23 17:29 ` Boeuf, Sebastien
2022-02-24 6:27 ` Gerd Hoffmann
2022-02-24 14:35 ` Boeuf, Sebastien
2022-02-22 15:53 ` [PATCH 2/3] OvmfPkg: CloudHv: Retrieve RSDP address from PVH Boeuf, Sebastien
2022-02-23 11:31 ` [edk2-devel] " Gerd Hoffmann
2022-02-24 14:41 ` Boeuf, Sebastien
2022-02-25 9:34 ` Gerd Hoffmann [this message]
2022-02-22 15:53 ` [PATCH 3/3] OvmfPkg: CloudHv: Rely on PVH memmap instead of CMOS 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=20220225093405.2rwmieyt4ue3ytg2@sirius.home.kraxel.org \
--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