From: "Ni, Ray" <ray.ni@intel.com>
To: 'Gerd Hoffmann' <kraxel@redhat.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/6] Substract TME-MK KEY_ID_BITS from CPU max PA
Date: Thu, 30 Mar 2023 02:26:25 +0000 [thread overview]
Message-ID: <MN6PR11MB8244731906284880899B05CA8C8E9@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <17509A92F1FF60E5.28404@groups.io>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
Tom,
I would assume this won't break any AMD system because the CPUID bit doesn't declare this feature.
Gerd,
This is needed by Intel platform for TME-MK. Can you help to analyze if it has any impact to OVMF? I assume no.
Thanks,
Ray
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ni, Ray
Sent: Tuesday, March 28, 2023 10:10 PM
To: devel@edk2.groups.io
Cc: 'Gerd Hoffmann' <kraxel@redhat.com>; Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH 0/6] Substract TME-MK KEY_ID_BITS from CPU max PA
Gerd, Tom,
Can you please review this patch series?
thanks,
ray
________________________________
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> on behalf of Ni, Ray <ray.ni@intel.com<mailto:ray.ni@intel.com>>
Sent: Wednesday, March 22, 2023 7:56:44 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>>
Subject: [edk2-devel] [PATCH 0/6] Substract TME-MK KEY_ID_BITS from CPU max PA
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
[-- Attachment #2: Type: text/html, Size: 5972 bytes --]
next prev parent reply other threads:[~2023-03-30 2:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <174E9488256AAAA5.22739@groups.io>
2023-03-28 14:10 ` [edk2-devel] [PATCH 0/6] Substract TME-MK KEY_ID_BITS from CPU max PA Ni, Ray
2023-03-28 14:13 ` Ni, Ray
[not found] ` <17509A92F1FF60E5.28404@groups.io>
2023-03-30 2:26 ` Ni, Ray [this message]
2023-03-30 7:25 ` Gerd Hoffmann
2023-03-30 8:41 ` Ni, Ray
2023-03-30 9:03 ` Gerd Hoffmann
2023-03-31 7:24 ` Ni, Ray
[not found] ` <17517033A2B187E0.12651@groups.io>
2023-03-31 8:02 ` Ni, Ray
2023-03-31 9:26 ` Gerd Hoffmann
2023-03-30 15:28 ` Lendacky, Thomas
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=MN6PR11MB8244731906284880899B05CA8C8E9@MN6PR11MB8244.namprd11.prod.outlook.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