public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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 v4 0/5] Change CpuS3Data memory type and address limitation
Date: Wed, 15 Aug 2018 16:00:27 +0200	[thread overview]
Message-ID: <f0a24585-0f1a-1233-e4d6-a4e3f7ac6c7f@redhat.com> (raw)
In-Reply-To: <62e220a5-7521-0992-86f7-7fe35cc55aa1@redhat.com>

On 08/15/18 15:14, Laszlo Ersek wrote:
> On 08/15/18 04:14, 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                |  51 +++++---
>>  UefiCpuPkg/CpuS3DataDxe/CpuS3DataDxe.inf           |   1 +
>>  UefiCpuPkg/Include/AcpiCpuData.h                   |  34 ++----
>>  .../DxeRegisterCpuFeaturesLib.c                    |  67 -----------
>>  .../PeiRegisterCpuFeaturesLib.c                    | 131 ---------------------
>>  .../RegisterCpuFeaturesLib/RegisterCpuFeatures.h   |  20 ----
>>  .../RegisterCpuFeaturesLib.c                       |  92 +++++++++++++++
>>  UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c                  |  31 +++--
>>  8 files changed, 155 insertions(+), 272 deletions(-)
>>
> 
> Looks like this series is now fully reviewed.
> 
> I will now do some regression-testing.

Tested on the Q35 machine type, built into OVMF with -D SMM_REQUIRE, on
top of commit 22ec06c8aaa1.

I used the tests described here:
<https://github.com/tianocore/tianocore.github.io/wiki/Testing-SMM-with-QEMU,-KVM-and-libvirt>.

- with Linux guests:
  Fedora (IA32); Fedora (IA32X64); RHEL7 (IA32X64)

- with Windows guests (all IA32X64):
  7; Server 2008 R2; 8.1; Server 2012 R2; 10

For patches #1 through #4:
Tested-by: Laszlo Ersek <lersek@redhat.com>

(Patch #5 is not testable with OVMF, because no module in OVMF uses
RegisterCpuFeaturesLib -- the lib class isn't resolved under OvmfPkg/ to
any instance at all.)

Please hold off pushing the series until after the upcoming stable tag.

Thanks,
Laszlo


      reply	other threads:[~2018-08-15 14:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15  2:14 [Patch v4 0/5] Change CpuS3Data memory type and address limitation Eric Dong
2018-08-15  2:14 ` [Patch v4 1/5] UefiCpuPkg/PiSmmCpuDxeSmm: Use GDT/IDT saved in Smram Eric Dong
2018-08-15  5:40   ` Ni, Ruiyu
2018-08-15 13:03   ` Laszlo Ersek
2018-08-15  2:14 ` [Patch v4 2/5] UefiCpuPkg/AcpiCpuData.h: Remove AcpiNVS and Below 4G limitation Eric Dong
2018-08-15  2:14 ` [Patch v4 3/5] UefiCpuPkg/CpuS3DataDxe: Change Memory Type and address limitation Eric Dong
2018-08-15  5:40   ` Ni, Ruiyu
2018-08-15 13:11   ` Laszlo Ersek
2018-08-15 13:12   ` Marvin Häuser
2018-08-15 15:30     ` Laszlo Ersek
2018-08-16  0:56       ` Dong, Eric
2018-08-16 12:30         ` Laszlo Ersek
2018-08-16 12:59           ` Marvin Häuser
2018-08-17  1:51             ` Dong, Eric
2018-08-15  2:14 ` [Patch v4 4/5] UefiCpuPkg/CpuS3DataDxe: Remove below 4G limitation Eric Dong
2018-08-15  2:14 ` [Patch v4 5/5] UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation Eric Dong
2018-08-15 13:14 ` [Patch v4 0/5] Change CpuS3Data memory type and address limitation Laszlo Ersek
2018-08-15 14:00   ` 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=f0a24585-0f1a-1233-e4d6-a4e3f7ac6c7f@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