From: Laszlo Ersek <lersek@redhat.com>
To: Eric Dong <eric.dong@intel.com>, edk2-devel@lists.01.org
Cc: Marvin H user <Marvin.Haeuser@outlook.com>,
Fan Jeff <vanjeff_919@hotmail.com>, Ruiyu Ni <ruiyu.ni@intel.com>
Subject: Re: [Patch v3 0/5] Change CpuS3Data memory type and address limitation
Date: Fri, 10 Aug 2018 18:39:38 +0200 [thread overview]
Message-ID: <b4fa4124-eac0-e34f-6c24-bba57cb0b5da@redhat.com> (raw)
In-Reply-To: <20180810041909.12776-1-eric.dong@intel.com>
Eric,
On 08/10/18 06:19, Eric Dong wrote:
> Because CpuS3Data memory will be copy to smram at SmmReadToLock point by PiSmmCpuDxeSmm driver,
> the memory type no need to be ACPI NVS type, also the address not limit to below 4G.
>
> This change remove the limit of ACPI NVS memory type and below 4G.
>
> Cc: Marvin H user <Marvin.Haeuser@outlook.com>
> Cc: Fan Jeff <vanjeff_919@hotmail.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
>
>
> Eric Dong (5):
> UefiCpuPkg/PiSmmCpuDxeSmm: Use GDT/IDT saved in Smram.
> UefiCpuPkg/AcpiCpuData.h: Remove AcpiNVS and Below 4G limitation.
> UefiCpuPkg/CpuS3DataDxe: Change Memory Type and address limitation.
> UefiCpuPkg/CpuS3DataDxe: Remove below 4G limitation.
> UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation.
>
> UefiCpuPkg/CpuS3DataDxe/CpuS3Data.c | 60 +++++++---
> UefiCpuPkg/Include/AcpiCpuData.h | 34 ++----
> .../DxeRegisterCpuFeaturesLib.c | 67 -----------
> .../PeiRegisterCpuFeaturesLib.c | 131 ---------------------
> .../RegisterCpuFeaturesLib/RegisterCpuFeatures.h | 20 ----
> .../RegisterCpuFeaturesLib.c | 92 +++++++++++++++
> UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c | 11 +-
> 7 files changed, 153 insertions(+), 262 deletions(-)
>
Because patches #1 and #3 could still be updated, I'm not going to test
the series at this time. If you decide to replace the global variables
from patch #1 with local variables, using an incremental change, *and*
for patch #3, AllocateZeroPages() does not prove useful, then I'll test
this version. Otherwise I'd like to test the next version (v4).
Thanks!
Laszlo
prev parent reply other threads:[~2018-08-10 16:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 4:19 [Patch v3 0/5] Change CpuS3Data memory type and address limitation Eric Dong
2018-08-10 4:19 ` [Patch v3 1/5] UefiCpuPkg/PiSmmCpuDxeSmm: Use GDT/IDT saved in Smram Eric Dong
2018-08-10 15:40 ` Laszlo Ersek
2018-08-13 1:54 ` Dong, Eric
2018-08-14 12:51 ` Laszlo Ersek
2018-08-13 5:42 ` Ni, Ruiyu
2018-08-10 4:19 ` [Patch v3 2/5] UefiCpuPkg/AcpiCpuData.h: Remove AcpiNVS and Below 4G limitation Eric Dong
2018-08-10 15:58 ` Laszlo Ersek
2018-08-13 5:42 ` Ni, Ruiyu
2018-08-10 4:19 ` [Patch v3 3/5] UefiCpuPkg/CpuS3DataDxe: Change Memory Type and address limitation Eric Dong
2018-08-10 16:12 ` Laszlo Ersek
2018-08-10 16:15 ` Laszlo Ersek
2018-08-13 1:50 ` Dong, Eric
2018-08-13 5:38 ` Ni, Ruiyu
2018-08-13 5:52 ` Ni, Ruiyu
2018-08-14 12:49 ` Laszlo Ersek
2018-08-10 4:19 ` [Patch v3 4/5] UefiCpuPkg/CpuS3DataDxe: Remove below 4G limitation Eric Dong
2018-08-10 16:22 ` Laszlo Ersek
2018-08-13 5:41 ` Ni, Ruiyu
2018-08-10 4:19 ` [Patch v3 5/5] UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation Eric Dong
2018-08-10 16:34 ` Laszlo Ersek
2018-08-13 5:41 ` Ni, Ruiyu
2018-08-10 16:39 ` Laszlo Ersek [this message]
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=b4fa4124-eac0-e34f-6c24-bba57cb0b5da@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