public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, oleksiyy@ami.com
Cc: liming.gao@intel.com, michael.d.kinney@intel.com,
	dandan.bi@intel.com, ray.ni@intel.com, rahul1.kumar@intel.com,
	Felixp@ami.com
Subject: Re: [edk2-devel] [PATCH V3 0/4] Add New Memory Attributes
Date: Mon, 6 Jul 2020 11:57:22 +0200	[thread overview]
Message-ID: <102401fb-a667-09e0-cfc0-ad3b86f27a01@redhat.com> (raw)
In-Reply-To: <20200702205039.52400-1-oleksiyy@ami.com>

On 07/02/20 22:50, Oleksiy Yakovlev wrote:
> This series of patches add usage of new memory
> attributes EFI_MEMORY_SP and EFI_MEMORY_CPU_CRYPTO,
> introduced in UEFI2.8 (mantis 1919 and 1872).
> First patch fix typos in description and introduce two 
> bitmasks for all memory type attributes.
> Second and fourth patches get rid of multiple memory attributes
> bitmasks definitions trough multiple files and headers,
> and replace them with new common definitions from MdePkg.
> Third patch includes WP attribute into cache type mask in
> CpuDexe.h to make next change in this file more clear.
> 
> Oleksiy Yakovlev (4):
>   MdePkg: Add New Memory Attributes
>   MdeModulePkg: Add New Memory Attributes
>   UefiCpuPkg: Update EFI_MEMORY_CACHETYPE_MASK definition
>   UefiCpuPkg: Add New Memory Attributes
> 
>  MdeModulePkg/Core/Dxe/Gcd/Gcd.c                    | 11 ++---------
>  MdeModulePkg/Core/Dxe/Mem/Page.c                   |  9 +++------
>  MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c      |  7 ++-----
>  MdeModulePkg/Core/PiSmmCore/PiSmmIpl.c             | 10 ++--------
>  MdePkg/Include/Uefi/UefiSpec.h                     | 10 ++++++++--
>  UefiCpuPkg/CpuDxe/CpuDxe.c                         | 11 ++++-------
>  UefiCpuPkg/CpuDxe/CpuDxe.h                         | 12 ------------
>  UefiCpuPkg/CpuDxe/CpuPageTable.c                   |  6 +++---
>  UefiCpuPkg/PiSmmCpuDxeSmm/SmmCpuMemoryManagement.c |  2 +-
>  9 files changed, 25 insertions(+), 53 deletions(-)
> 

series
Tested-by: Laszlo Ersek <lersek@redhat.com>

Meaning my usual OVMF regression tests, and (due to patch#2) an
ArmVirtQemu boot test on AARCH64 KVM too.

Thanks
Laszlo


  parent reply	other threads:[~2020-07-06  9:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 20:50 [PATCH V3 0/4] Add New Memory Attributes Oleksiy Yakovlev
2020-07-02 20:50 ` [PATCH V3 1/4] MdePkg: " Oleksiy Yakovlev
2020-07-06  9:11   ` [edk2-devel] " Laszlo Ersek
2020-07-02 20:50 ` [PATCH V3 2/4] MdeModulePkg: " Oleksiy Yakovlev
2020-07-06  9:13   ` [edk2-devel] " Laszlo Ersek
2020-07-13 16:12     ` Laszlo Ersek
2020-07-02 20:50 ` [PATCH V3 3/4] UefiCpuPkg: Update EFI_MEMORY_CACHETYPE_MASK definition Oleksiy Yakovlev
2020-07-06  9:16   ` [edk2-devel] " Laszlo Ersek
2020-07-13 16:13   ` Laszlo Ersek
2020-07-14  0:13   ` Dong, Eric
2020-07-02 20:50 ` [PATCH V3 4/4] UefiCpuPkg: Add New Memory Attributes Oleksiy Yakovlev
2020-07-13 16:14   ` [edk2-devel] " Laszlo Ersek
2020-07-14  0:16   ` Dong, Eric
2020-07-06  9:57 ` Laszlo Ersek [this message]
2020-07-15 15:07 ` [edk2-devel] [PATCH V3 0/4] " Laszlo Ersek
2023-11-17  8:07 ` Dhaval Sharma
2023-11-17  8:25   ` Laszlo Ersek
2023-11-20  4:59     ` Dhaval Sharma
2023-11-21 15:03       ` Laszlo Ersek

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=102401fb-a667-09e0-cfc0-ad3b86f27a01@redhat.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