public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: Min Xu <min.m.xu@intel.com>, devel@edk2.groups.io
Cc: Erdem Aktas <erdemaktas@google.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	James Bottomley <jejb@linux.ibm.com>,
	Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [PATCH V1 0/3] Customize lazy-accepted memory size for TDVF
Date: Tue, 3 Jan 2023 09:39:00 -0600	[thread overview]
Message-ID: <5cd96451-5b40-c42e-b6b1-819034052a7c@amd.com> (raw)
In-Reply-To: <20221226013338.1924-1-min.m.xu@intel.com>

On 12/25/22 19:33, Min Xu wrote:
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=4181
> 
> Current lazy-accept accepts the memory under address of 4G. To improve
> boot performance further more, we introduce the feature of customizing
> the physical end address of lazy-accept in build time.
> 
> The end address is indicated by PcdAcceptMemoryEndAddress. It means it
> accepts the memory under PcdAcceptMemoryEndAddress. The default value
> and the max value is 4G. This is to be consistent with the current rule
> (accept memory under 4G).
> 
> In IntelTdxX64 PcdAcceptMemoryEndAddress can be customized on-demand in
> build-time by adding -D ACCEPT_MEMORY_END_ADDRESS=512 in build command.

Wasn't there an agreement against modifying the build environment like 
this for memory acceptance? I realize this is not an accept / no-accept 
build environment change, but still...

Thanks,
Tom

> 
> Code: https://github.com/mxu9/edk2/tree/CustomizeLazyAcceptSize.v1
> 
> Cc: Erdem Aktas <erdemaktas@google.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: James Bottomley <jejb@linux.ibm.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Signed-off-by: Min Xu <min.m.xu@intel.com>
> 
> Min M Xu (3):
>    OvmfPkg: Customize lazy-accept's end address
>    OvmfPkg/PeilessStartupLib: Update ConstructFwHobList for lazy-accept
>    OvmfPkg/PlatformPei: Adjust LowerMemorySize in PublishPeiMemory
> 
>   OvmfPkg/IntelTdx/IntelTdxX64.dsc              |  8 ++++
>   OvmfPkg/Library/PeilessStartupLib/Hob.c       | 25 +++++++++----
>   .../PeilessStartupLib/PeilessStartupLib.inf   |  1 +
>   OvmfPkg/Library/PlatformInitLib/IntelTdx.c    | 37 ++++++++++++++-----
>   .../PlatformInitLib/PlatformInitLib.inf       |  1 +
>   OvmfPkg/OvmfPkg.dec                           |  2 +
>   OvmfPkg/PlatformPei/MemDetect.c               | 13 +++++++
>   OvmfPkg/PlatformPei/PlatformPei.inf           |  1 +
>   8 files changed, 72 insertions(+), 16 deletions(-)
> 

      parent reply	other threads:[~2023-01-03 15:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26  1:33 [PATCH V1 0/3] Customize lazy-accepted memory size for TDVF Min Xu
2022-12-26  1:33 ` [PATCH V1 1/3] OvmfPkg: Customize lazy-accept's end address Min Xu
2022-12-26  1:33 ` [PATCH V1 2/3] OvmfPkg/PeilessStartupLib: Update ConstructFwHobList for lazy-accept Min Xu
2022-12-26  1:33 ` [PATCH V1 3/3] OvmfPkg/PlatformPei: Adjust LowerMemorySize in PublishPeiMemory Min Xu
2023-01-02 10:36 ` [PATCH V1 0/3] Customize lazy-accepted memory size for TDVF Gerd Hoffmann
2023-01-16 12:01   ` [edk2-devel] " Min Xu
2023-01-17  9:43     ` Gerd Hoffmann
2023-01-03 15:39 ` Lendacky, Thomas [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=5cd96451-5b40-c42e-b6b1-819034052a7c@amd.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