From: "Min Xu" <min.m.xu@intel.com>
To: devel@edk2.groups.io
Cc: Min Xu <min.m.xu@intel.com>, Erdem Aktas <erdemaktas@google.com>,
Gerd Hoffmann <kraxel@redhat.com>,
James Bottomley <jejb@linux.ibm.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: [PATCH 0/2] Fix 2 issues in TDVF
Date: Tue, 31 May 2022 22:31:15 +0800 [thread overview]
Message-ID: <cover.1654007213.git.min.m.xu@intel.com> (raw)
During the integration test with TDX upstreaming KVM/QEMU there are 2
issues are found. This patch-set are to fix these 2 issue.
- Fix TDVMCALL error in ApRunLoop.nasm
- Search EFI_RESOURCE_MEMORY_UNACCEPTED for Fw hoblist
Cc: Erdem Aktas <erdemaktas@google.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: James Bottomley <jejb@linux.ibm.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Min Xu <min.m.xu@intel.com>
*** BLURB HERE ***
Min Xu (2):
OvmfPkg: Fix TDVMCALL error in ApRunLoop.nasm
OvmfPkg: Search EFI_RESOURCE_MEMORY_UNACCEPTED for Fw hoblist
OvmfPkg/Library/PeilessStartupLib/Hob.c | 4 +++-
OvmfPkg/TdxDxe/X64/ApRunLoop.nasm | 3 ++-
2 files changed, 5 insertions(+), 2 deletions(-)
--
2.29.2.windows.2
next reply other threads:[~2022-05-31 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 14:31 Min Xu [this message]
2022-05-31 14:31 ` [PATCH 1/2] OvmfPkg: Fix TDVMCALL error in ApRunLoop.nasm Min Xu
2022-06-01 8:49 ` Gerd Hoffmann
2022-05-31 14:31 ` [PATCH 2/2] OvmfPkg: Search EFI_RESOURCE_MEMORY_UNACCEPTED for Fw hoblist Min Xu
2022-06-01 8:53 ` [edk2-devel] " Gerd Hoffmann
2022-06-02 8:47 ` [PATCH 0/2] Fix 2 issues in TDVF Yao, Jiewen
[not found] ` <16F4C173DC6EFECF.9239@groups.io>
2022-06-02 9:12 ` [edk2-devel] " Yao, Jiewen
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.1654007213.git.min.m.xu@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