From: "Ni, Ray" <ray.ni@intel.com>
To: devel@edk2.groups.io
Subject: [PATCH 0/6] Substract TME-MK KEY_ID_BITS from CPU max PA
Date: Wed, 22 Mar 2023 07:56:44 +0800 [thread overview]
Message-ID: <20230321235650.675-1-ray.ni@intel.com> (raw)
Ray Ni (6):
MdePkg: Add TME-MK related CPUID and MSR definitions
UefiCpuPkg/MtrrTest: Only claim CPUID max leaf as 1
UefiCpuPkg/MtrrLib: Substract TME-MK KEY_ID_BITS from CPU max PA
UefiCpuPkg/CpuDxe: Refactor to use CPUID definitions
UefiCpuPkg/CpuDxe: Substract TME-MK KEY_ID_BITS from CPU max PA
UefiCpuPkg/MtrrTest: Add test cases for TME-MK enable case
.../Include/Register/Intel/ArchitecturalMsr.h | 106 ++++++++++++++-
MdePkg/Include/Register/Intel/Cpuid.h | 9 +-
UefiCpuPkg/CpuDxe/CpuDxe.c | 38 ++++--
UefiCpuPkg/CpuDxe/CpuDxe.h | 3 +-
UefiCpuPkg/Library/MtrrLib/MtrrLib.c | 24 +++-
.../MtrrLib/UnitTest/MtrrLibUnitTest.c | 18 +--
.../MtrrLib/UnitTest/MtrrLibUnitTest.h | 3 +-
UefiCpuPkg/Library/MtrrLib/UnitTest/Support.c | 126 ++++++++++++++----
8 files changed, 278 insertions(+), 49 deletions(-)
--
2.39.1.windows.1
next reply other threads:[~2023-03-21 23:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 23:56 Ni, Ray [this message]
2023-03-21 23:56 ` [PATCH 1/6] MdePkg: Add TME-MK related CPUID and MSR definitions Ni, Ray
2023-03-29 22:14 ` Michael D Kinney
2023-03-29 22:24 ` Michael D Kinney
2023-03-21 23:56 ` [PATCH 2/6] UefiCpuPkg/MtrrTest: Only claim CPUID max leaf as 1 Ni, Ray
2023-03-29 22:22 ` Michael D Kinney
2023-03-21 23:56 ` [PATCH 3/6] UefiCpuPkg/MtrrLib: Substract TME-MK KEY_ID_BITS from CPU max PA Ni, Ray
2023-03-29 22:22 ` Michael D Kinney
2023-03-21 23:56 ` [PATCH 4/6] UefiCpuPkg/CpuDxe: Refactor to use CPUID definitions Ni, Ray
2023-03-29 22:22 ` Michael D Kinney
2023-03-21 23:56 ` [PATCH 5/6] UefiCpuPkg/CpuDxe: Substract TME-MK KEY_ID_BITS from CPU max PA Ni, Ray
2023-03-29 22:23 ` Michael D Kinney
2023-03-21 23:56 ` [PATCH 6/6] UefiCpuPkg/MtrrTest: Add test cases for TME-MK enable case Ni, Ray
2023-03-29 22:23 ` Michael D Kinney
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=20230321235650.675-1-ray.ni@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