public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"Dong, Eric" <eric.dong@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation.
Date: Thu, 9 Aug 2018 03:18:08 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BDC96E8@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <12da7e20-6f8e-0e3b-f026-42041e6b2415@redhat.com>

> -----Original Message-----
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Thursday, August 9, 2018 5:29 AM
> To: Dong, Eric <eric.dong@intel.com>; edk2-devel@lists.01.org
> Cc: Ni, Ruiyu <ruiyu.ni@intel.com>
> Subject: Re: [edk2] [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib:
> Combine implementation.
> 
> On 08/08/18 09:40, Eric Dong wrote:
> > V1 changes:
> >> Current code logic can't confirm CpuS3DataDxe driver start before
> >> CpuFeaturesDxe driver. So the assumption in CpuFeaturesDxe not valid.
> >> Add implementation for AllocateAcpiCpuData function to remove this
> >> assumption.
> >
> > V2 changes:
> >> Because CpuS3Data memory will be copy to smram at SmmReadToLock
> >> point, so 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.
> 
> I'm returning to this patch (v2 1/2) after my other comments (for v2 2/2).
> 
> It seems that allocating ACPI_CPU_DATA in BootServicesData type memory
> breaks at least the docs / specs in "UefiCpuPkg/Include/AcpiCpuData.h",
> even if we do the BootServicesData allocation in RegisterCpuFeaturesLib
> instances (i.e. in CpuFeaturesPei / CpuFeaturesDxe), and not in
> CpuS3DataDxe.
> 
> With that in mind, should we return to your v1 patch,
> "UefiCpuPkg/RegisterCpuFeaturesLib: Implement AllocateAcpiCpuData
> function"?
> 
> And, looking back at my question (4) there, where I suggested
> AllocatePeiAccessiblePages() -- I'm now thinking that it does not apply,
> because the ACPI_CPU_DATA spec in "UefiCpuPkg/Include/AcpiCpuData.h"
> requires the 4GB limit.

I guess Eric forgot to update the comments in AcpiCpuData.h regarding the
4GB/NVS restriction.
We've reviewed the whole producer/consumer code and came to the conclusion
that 4GB/NVS restriction is unnecessary.

> 
> So, currently I think that your v1 patch is best, just add the Reported-by and
> Suggested-by tags, plus the TianoCore BZ reference.
> 
> Sorry that I've taken so long to grasp the implications. (Anyway we're now in
> the quiet period.)
> 
> Thanks,
> Laszlo

  reply	other threads:[~2018-08-09  3:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08  7:40 [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation Eric Dong
2018-08-08  7:40 ` [Patch v2 2/2] UefiCpuPkg/CpuS3DataDxe: Change Memory Type and address limitation Eric Dong
2018-08-08 16:55   ` Laszlo Ersek
2018-08-09  3:22     ` Ni, Ruiyu
2018-08-10  3:39     ` Dong, Eric
2018-08-10  4:00       ` 答复: " Fan Jeff
2018-08-10  4:01         ` 答复: " Fan Jeff
2018-08-08 14:45 ` [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation Laszlo Ersek
2018-08-08 21:28 ` Laszlo Ersek
2018-08-09  3:18   ` Ni, Ruiyu [this message]
2018-08-09 11:21     ` Laszlo Ersek
2018-08-10  3:10       ` Dong, Eric
2018-08-09 11:29     ` 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=734D49CCEBEEF84792F5B80ED585239D5BDC96E8@SHSMSX104.ccr.corp.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