From: "Laszlo Ersek" <lersek@redhat.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
devel@edk2.groups.io, Eric Dong <eric.dong@intel.com>,
Ray Ni <ray.ni@intel.com>
Cc: Rahul Kumar <rahul1.kumar@intel.com>,
Brijesh Singh <brijesh.singh@amd.com>,
Garrett Kirkendall <garrett.kirkendall@amd.com>
Subject: Re: [PATCH v2 1/1] UefiCpuPkg/MpInitLib: Reduce reset vector memory pressure
Date: Mon, 19 Oct 2020 23:51:43 +0200 [thread overview]
Message-ID: <c81aef5f-b26c-5fbc-ff65-0025632d19e2@redhat.com> (raw)
In-Reply-To: <0794f733-ca18-3b6e-b82f-ac62fa94a216@amd.com>
On 10/19/20 17:02, Tom Lendacky wrote:
> On 10/2/20 11:42 AM, Tom Lendacky wrote:
>> On 9/24/20 10:03 AM, Laszlo Ersek wrote:
>>> On 09/24/20 15:30, Tom Lendacky wrote:
>>>> On 9/24/20 1:22 AM, Laszlo Ersek wrote:
>>>>> On 09/23/20 20:04, Tom Lendacky wrote:
>>>>>> From: Tom Lendacky <thomas.lendacky@amd.com>
>>>>>>
>>>>>> The AP reset vector stack allocation is only required if running as an
>>>>>> SEV-ES guest. Since the reset vector allocation is below 1MB in memory,
>>>>>> eliminate the requirement for bare-metal systems and non SEV-ES guests
>>>>>> to allocate the extra stack area, which can be large if the
>>>>>> PcdCpuMaxLogicalProcessorNumber value is large, and also remove the
>>>>>> CPU_STACK_ALIGNMENT alignment.
>>>>>>
>>>>>> Fixes: 7b7508ad784d ("UefiCpuPkg: Allow AP booting under SEV-ES")
>>>>>> Cc: Garrett Kirkendall <garrett.kirkendall@amd.com>
>>>>>> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
>>>>>> ---
>>>>>> UefiCpuPkg/Library/MpInitLib/MpLib.c | 36 +++++++++-----------
>>>>>> 1 file changed, 17 insertions(+), 19 deletions(-)
>>>>>>
>>>>>> diff --git a/UefiCpuPkg/Library/MpInitLib/MpLib.c
>>>>>> b/UefiCpuPkg/Library/MpInitLib/MpLib.c
>>>>>> index 07426274f639..a9708c6479d2 100644
>>>>>> --- a/UefiCpuPkg/Library/MpInitLib/MpLib.c
>>>>>> +++ b/UefiCpuPkg/Library/MpInitLib/MpLib.c
>>>>>> @@ -1141,20 +1141,6 @@ RestoreWakeupBuffer(
>>>>>> );
>>>>>> }
>>>>>> -/**
>>>>>> - Calculate the size of the reset stack.
>>>>>> -
>>>>>> - @return Total amount of memory required for stacks
>>>>>> -**/
>>>>>> -STATIC
>>>>>> -UINTN
>>>>>> -GetApResetStackSize (
>>>>>> - VOID
>>>>>> - )
>>>>>> -{
>>>>>> - return AP_RESET_STACK_SIZE *
>>>>>> PcdGet32(PcdCpuMaxLogicalProcessorNumber);
>>>>>> -}
>>>>>> -
>>>>>> /**
>>>>>> Calculate the size of the reset vector.
>>>>>> @@ -1170,11 +1156,23 @@ GetApResetVectorSize (
>>>>>> {
>>>>>> UINTN Size;
>>>>>> - Size = ALIGN_VALUE (AddressMap->RendezvousFunnelSize +
>>>>>> - AddressMap->SwitchToRealSize +
>>>>>> - sizeof (MP_CPU_EXCHANGE_INFO),
>>>>>> - CPU_STACK_ALIGNMENT);
>>>>>> - Size += GetApResetStackSize ();
>>>>>> + Size = AddressMap->RendezvousFunnelSize +
>>>>>> + AddressMap->SwitchToRealSize +
>>>>>> + sizeof (MP_CPU_EXCHANGE_INFO);
>>>>>> +
>>>>>> + //
>>>>>> + // The AP reset stack is only used by SEV-ES guests. Do not add to
>>>>>> the
>>>>>> + // allocation if SEV-ES is not enabled.
>>>>>> + //
>>>>>> + if (PcdGetBool (PcdSevEsIsEnabled)) {
>>>>>> + //
>>>>>> + // Stack location is based on APIC ID, so use the total number of
>>>>>> + // processors for calculating the total stack area.
>>>>>> + //
>>>>>> + Size += AP_RESET_STACK_SIZE *
>>>>>> PcdGet32(PcdCpuMaxLogicalProcessorNumber);
>>>>>> +
>>>>>> + Size = ALIGN_VALUE (Size, CPU_STACK_ALIGNMENT);
>>>>>> + }
>>>>>> return Size;
>>>>>> }
>>>>>>
>>>>>
>>>>> - I don't remember if it's required that the APIC ID space be densely
>>>>> populated. For example, if we have a topology with 7 possible (=
>>>>> maximum) logical CPUs, I'm unsure if a spec forbids any of those CPUs
>>>>> from having APIC ID 7. That could cause a problem in
>>>>> MpInitLibSevEsAPReset(), I assume.
>>>>>
>>>>> Anyway: that's a different topic. This patch looks OK to me because it
>>>>> only spells out the existent assumption wrt. APIC IDs vs.
>>>>> PcdCpuMaxLogicalProcessorNumber, plus it does solve the problem it wants
>>>>> to solve.
>>>>>
>>>>> - I was a bit surprised at first upon seeing the reordering of alignment
>>>>> vs. addition. But AP_RESET_STACK_SIZE is a whole multiple of
>>>>> CPU_STACK_ALIGNMENT. So adding AP_RESET_STACK_SIZE to Size n times as
>>>>> first step, does not change the congruence class of Size modulo
>>>>> CPU_STACK_ALIGNMENT. Therefore ALIGN_VALUE() will increment Size by the
>>>>> same value, regardless of whether it's done before or after the
>>>>> AP_RESET_STACK_SIZE additions.
>>>>
>>>> Ah, yes, I did change that order. I could submit one more version that
>>>> puts the ALIGN_VALUE back to the original position and fix the PcdGet32
>>>> space if that is desired (but, as you determined, it doesn't change the
>>>> resulting value).
>>>
>>> Given that the stack grows down, one could plausibly claim that the
>>> variant seen in this patch (= align at last) is *more* intuitive.
>>>
>>> I'm OK with this version merged (with the whitespace fixed up).
>>
>> Any concern from the maintainers on this? Are you waiting on me for
>> anything? Just want to check...
>
> Another ping to see what the status of this patch is...
... I guess we might as well break the process for a noble purpose,
every once in a while, so I went ahead and merged this... with just my R-b.
- [lersek@redhat.com: supply missing space character after "PcdGet32"]
- commit 93edd1887e34
- https://github.com/tianocore/edk2/pull/1031
Thanks
Laszlo
>>>> I'm surprised that PatchCheck.py didn't pick up on the
>>>> spacing with PcdGet32.
>>>
>>> Or maybe ECC should warn about it in CI?...
>>>
>>> Thanks
>>> Laszlo
>>>
>
next prev parent reply other threads:[~2020-10-19 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 18:04 [PATCH v2 1/1] UefiCpuPkg/MpInitLib: Reduce reset vector memory pressure Lendacky, Thomas
2020-09-24 6:22 ` Laszlo Ersek
2020-09-24 13:30 ` Lendacky, Thomas
2020-09-24 15:03 ` Laszlo Ersek
2020-10-02 16:42 ` Lendacky, Thomas
2020-10-19 15:02 ` Lendacky, Thomas
2020-10-19 21:51 ` Laszlo Ersek [this message]
2020-09-25 16:09 ` [edk2-devel] " Brian J. Johnson
2020-09-25 16:52 ` Lendacky, Thomas
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=c81aef5f-b26c-5fbc-ff65-0025632d19e2@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