From: "Ni, Ray" <ray.ni@intel.com>
To: "Xie, Yuanhao" <yuanhao.xie@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
"Dong, Eric" <eric.dong@intel.com>,
"Kumar, Rahul R" <rahul.r.kumar@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [Patch V3 4/5] UefiCpuPkg: ApWakeupFunction directly use CpuMpData.
Date: Mon, 26 Jun 2023 09:36:45 +0000 [thread overview]
Message-ID: <MN6PR11MB8244807CB15ABF6EC7747B148C26A@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230626055705.57145-5-yuanhao.xie@intel.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
> -----Original Message-----
> From: Xie, Yuanhao <yuanhao.xie@intel.com>
> Sent: Monday, June 26, 2023 1:57 PM
> To: devel@edk2.groups.io
> Cc: Gerd Hoffmann <kraxel@redhat.com>; Dong, Eric <eric.dong@intel.com>; Ni,
> Ray <ray.ni@intel.com>; Kumar, Rahul R <rahul.r.kumar@intel.com>; Tom
> Lendacky <thomas.lendacky@amd.com>; Xie, Yuanhao
> <yuanhao.xie@intel.com>
> Subject: [Patch V3 4/5] UefiCpuPkg: ApWakeupFunction directly use CpuMpData.
>
> In the original design, once the APs finished executing their assembly
> code and switched to executing C code, they would enter a continuous
> loop within a function. In this function, they would collect CpuMpData
> using the MP_CPU_EXCHANGE_INFO mechanism. However, in the updated
> approach, CpuMpData can now be passed directly to the ApWakeUpFunction,
> bypassing the need for MP_CPU_EXCHANGE_INFO. This modification is made
> in preparation for eliminating the requirement of a second
> INIT-SIPI-SIPI sequence in the DXE phase.
>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Rahul Kumar <rahul1.kumar@intel.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
> Signed-off-by: Yuanhao Xie <yuanhao.xie@intel.com>
> ---
> UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm | 4 ++--
> UefiCpuPkg/Library/MpInitLib/MpLib.c | 12 +++---------
> UefiCpuPkg/Library/MpInitLib/X64/MpFuncs.nasm | 3 +--
> 3 files changed, 6 insertions(+), 13 deletions(-)
>
> diff --git a/UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm
> b/UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm
> index 59db4081d6..d117f09ef5 100644
> --- a/UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm
> +++ b/UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm
> @@ -197,8 +197,8 @@ CProcedureInvoke:
>
> push ebx ; Push ApIndex
> mov eax, esi
> - add eax, MP_CPU_EXCHANGE_INFO_OFFSET
> - push eax ; push address of exchange info data buffer
> + add eax, MP_CPU_EXCHANGE_INFO_FIELD (CpuMpData)
> + push dword [eax] ; push address of CpuMpData
>
> mov edi, esi
> add edi, MP_CPU_EXCHANGE_INFO_FIELD (CFunction)
> diff --git a/UefiCpuPkg/Library/MpInitLib/MpLib.c
> b/UefiCpuPkg/Library/MpInitLib/MpLib.c
> index 1252ee9673..15b24b1805 100644
> --- a/UefiCpuPkg/Library/MpInitLib/MpLib.c
> +++ b/UefiCpuPkg/Library/MpInitLib/MpLib.c
> @@ -710,17 +710,16 @@ PlaceAPInMwaitLoopOrRunLoop (
> /**
> This function will be called from AP reset code if BSP uses WakeUpAP.
>
> - @param[in] ExchangeInfo Pointer to the MP exchange info buffer
> + @param[in] CpuMpData Pointer to CPU MP Data
> @param[in] ApIndex Number of current executing AP
> **/
> VOID
> EFIAPI
> ApWakeupFunction (
> - IN MP_CPU_EXCHANGE_INFO *ExchangeInfo,
> - IN UINTN ApIndex
> + IN CPU_MP_DATA *CpuMpData,
> + IN UINTN ApIndex
> )
> {
> - CPU_MP_DATA *CpuMpData;
> UINTN ProcessorNumber;
> EFI_AP_PROCEDURE Procedure;
> VOID *Parameter;
> @@ -731,11 +730,6 @@ ApWakeupFunction (
> UINTN CurrentApicMode;
> AP_STACK_DATA *ApStackData;
>
> - //
> - // AP finished assembly code and begin to execute C code
> - //
> - CpuMpData = ExchangeInfo->CpuMpData;
> -
> //
> // AP's local APIC settings will be lost after received INIT IPI
> // We need to re-initialize them at here
> diff --git a/UefiCpuPkg/Library/MpInitLib/X64/MpFuncs.nasm
> b/UefiCpuPkg/Library/MpInitLib/X64/MpFuncs.nasm
> index 5bcdf7726b..40e80ffab4 100644
> --- a/UefiCpuPkg/Library/MpInitLib/X64/MpFuncs.nasm
> +++ b/UefiCpuPkg/Library/MpInitLib/X64/MpFuncs.nasm
> @@ -259,8 +259,7 @@ CProcedureInvoke:
> add rsp, 20h
>
> mov edx, ebx ; edx is ApIndex
> - mov ecx, esi
> - add ecx, MP_CPU_EXCHANGE_INFO_OFFSET ; rcx is address of exchange
> info data buffer
> + mov rcx, qword [esi + MP_CPU_EXCHANGE_INFO_FIELD (CpuMpData)]
>
> mov edi, esi
> add edi, MP_CPU_EXCHANGE_INFO_FIELD (CFunction)
> --
> 2.36.1.windows.1
next prev parent reply other threads:[~2023-06-26 9:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 5:57 [Patch V3 0/5] Eliminate the second INIT-SIPI-SIPI sequence Yuanhao Xie
2023-06-26 5:57 ` [Patch V3 1/5] UefiCpuPkg: Refactor the logic for placing APs in HltLoop Yuanhao Xie
2023-06-26 9:10 ` Ni, Ray
2023-06-26 5:57 ` [Patch V3 2/5] UefiCpuPkg: Refactor the logic for placing APs in Mwait/Runloop Yuanhao Xie
2023-06-26 9:10 ` Ni, Ray
2023-06-26 5:57 ` [Patch V3 3/5] UefiCpuPkg: Create MpHandOff Yuanhao Xie
2023-06-26 9:28 ` Ni, Ray
2023-06-28 8:57 ` Yuanhao Xie
2023-06-26 5:57 ` [Patch V3 4/5] UefiCpuPkg: ApWakeupFunction directly use CpuMpData Yuanhao Xie
2023-06-26 9:36 ` Ni, Ray [this message]
2023-06-26 5:57 ` [Patch V3 5/5] UefiCpuPkg: Eliminate the second INIT-SIPI-SIPI sequence Yuanhao Xie
2023-06-27 5:51 ` Ni, Ray
2023-06-28 8:52 ` Yuanhao Xie
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=MN6PR11MB8244807CB15ABF6EC7747B148C26A@MN6PR11MB8244.namprd11.prod.outlook.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