From: "Alexey Kardashevskiy via groups.io" <aik=amd.com@groups.io>
To: <devel@edk2.groups.io>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Michael D Kinney <michael.d.kinney@intel.com>,
Zhiguang Liu <zhiguang.liu@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Erdem Aktas <erdemaktas@google.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Michael Roth <michael.roth@amd.com>, Min Xu <min.m.xu@intel.com>,
Alexey Kardashevskiy <aik@amd.com>
Subject: [edk2-devel] [PATCH ovmf v4 0/5] Enable AMD SEV-ES DebugVirtualization
Date: Wed, 5 Jun 2024 12:09:41 +1000 [thread overview]
Message-ID: <20240605020946.1224515-1-aik@amd.com> (raw)
This is to prevent #DB interception on SEV-ES VM with
enabled DebugVirtualization feature.
The previous conversation is here:
https://edk2.groups.io/g/devel/topic/patch_ovmf_v3_0_5_enable/105863808
This is based on sha1
7772e339bdbb Chao Li "ArmVirtPkg: Enable the non-hardcode version FdtNorFlashQemuLib".
Please comment. Thanks.
Alexey Kardashevskiy (5):
MdePkg/Register/Amd: Define all bits from MSR_SEV_STATUS_REGISTER
MdePkg: Add AMD SEV features to PcdConfidentialComputingGuestAttr
OvmfPkg: Add AMD SEV-ES DebugVirtualization feature support
UefiCpuPkg: Add AMD SEV-ES features support
OvmfPkf: Enable AMD SEV-ES DebugVirtualization
MdePkg/Include/ConfidentialComputingGuestAttr.h | 15 +++-
MdePkg/Include/Register/Amd/Fam17Msr.h | 95 +++++++++++++++++++-
OvmfPkg/Include/Library/MemEncryptSevLib.h | 12 +++
OvmfPkg/Library/BaseMemEncryptSevLib/DxeMemEncryptSevLibInternal.c | 27 +++++-
OvmfPkg/Library/BaseMemEncryptSevLib/PeiMemEncryptSevLibInternal.c | 19 ++++
OvmfPkg/Library/BaseMemEncryptSevLib/SecMemEncryptSevLibInternal.c | 19 ++++
OvmfPkg/Library/CcExitLib/CcExitVcHandler.c | 8 ++
OvmfPkg/PlatformPei/AmdSev.c | 13 ++-
UefiCpuPkg/Library/MpInitLib/MpLib.c | 12 ++-
9 files changed, 205 insertions(+), 15 deletions(-)
--
2.44.0
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119458): https://edk2.groups.io/g/devel/message/119458
Mute This Topic: https://groups.io/mt/106496065/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2024-06-05 2:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 2:09 Alexey Kardashevskiy via groups.io [this message]
2024-06-05 2:09 ` [edk2-devel] [PATCH ovmf v4 1/5] MdePkg/Register/Amd: Define all bits from MSR_SEV_STATUS_REGISTER Alexey Kardashevskiy via groups.io
2024-06-05 18:33 ` Lendacky, Thomas via groups.io
2024-06-05 2:09 ` [edk2-devel] [PATCH ovmf v4 2/5] MdePkg: Add AMD SEV features to PcdConfidentialComputingGuestAttr Alexey Kardashevskiy via groups.io
2024-06-05 2:09 ` [edk2-devel] [PATCH ovmf v4 3/5] OvmfPkg: Add AMD SEV-ES DebugVirtualization feature support Alexey Kardashevskiy via groups.io
2024-06-05 18:47 ` Lendacky, Thomas via groups.io
2024-06-05 2:09 ` [edk2-devel] [PATCH ovmf v4 4/5] UefiCpuPkg: Add AMD SEV-ES features support Alexey Kardashevskiy via groups.io
2024-06-05 18:51 ` Lendacky, Thomas via groups.io
2024-06-05 2:09 ` [edk2-devel] [PATCH ovmf v4 5/5] OvmfPkf: Enable AMD SEV-ES DebugVirtualization Alexey Kardashevskiy via groups.io
2024-06-05 18:54 ` Lendacky, Thomas via groups.io
2024-06-12 1:24 ` Alexey Kardashevskiy via groups.io
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=20240605020946.1224515-1-aik@amd.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