From: "Dong, Eric" <eric.dong@intel.com>
To: "Ni, Ray" <ray.ni@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH v2 1/2] UefiCpuPkg/MpInitLib: increase NumApsExecuting only for ApInitConfig
Date: Mon, 10 Jun 2019 02:37:57 +0000 [thread overview]
Message-ID: <ED077930C258884BBCB450DB737E662259E4E78A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20190605054920.123184-2-ray.ni@intel.com>
Reviewed-by: Eric Dong <eric.dong@intel.com>
> -----Original Message-----
> From: Ni, Ray
> Sent: Wednesday, June 5, 2019 1:49 PM
> To: devel@edk2.groups.io
> Cc: Laszlo Ersek <lersek@redhat.com>; Dong, Eric <eric.dong@intel.com>
> Subject: [PATCH v2 1/2] UefiCpuPkg/MpInitLib: increase NumApsExecuting
> only for ApInitConfig
>
> NumApsExecuting is only used when InitFlag == ApInitConfig for counting the
> processor count.
>
> The patch changes Ia32 version of waking up vector assembly code to align to
> x64 version of waking up vector assembly code.
> After the change both versions of waking up vector increase
> NumApsExecuting when InitFlag == ApInitConfig.
>
> Signed-off-by: Ray Ni <ray.ni@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Cc: Eric Dong <eric.dong@intel.com>
> ---
> UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm
> b/UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm
> index 34b8705adb..b74046b76a 100644
> --- a/UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm
> +++ b/UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm
> @@ -1,5 +1,5 @@
> ;------------------------------------------------------------------------------ ; -;
> Copyright (c) 2015 - 2018, Intel Corporation. All rights reserved.<BR>
> +; Copyright (c) 2015 - 2019, Intel Corporation. All rights
> +reserved.<BR>
> ; SPDX-License-Identifier: BSD-2-Clause-Patent ; ; Module Name:
> @@ -81,12 +81,6 @@ Flat32Start: ; protected mode entry
> point
>
> mov esi, ebx
>
> - ; Increment the number of APs executing here as early as possible
> - ; This is decremented in C code when AP is finished executing
> - mov edi, esi
> - add edi, NumApsExecutingLocation
> - lock inc dword [edi]
> -
> mov edi, esi
> add edi, EnableExecuteDisableLocation
> cmp byte [edi], 0
> @@ -120,6 +114,12 @@ SkipEnableExecuteDisable:
> cmp dword [edi], 1 ; 1 == ApInitConfig
> jnz GetApicId
>
> + ; Increment the number of APs executing here as early as possible
> + ; This is decremented in C code when AP is finished executing
> + mov edi, esi
> + add edi, NumApsExecutingLocation
> + lock inc dword [edi]
> +
> ; AP init
> mov edi, esi
> add edi, LockLocation
> --
> 2.21.0.windows.1
next prev parent reply other threads:[~2019-06-10 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 5:49 [PATCH v2 0/2] Fix the issue that OS complains memory < 1MB changes across S3 Ni, Ray
2019-06-05 5:49 ` [PATCH v2 1/2] UefiCpuPkg/MpInitLib: increase NumApsExecuting only for ApInitConfig Ni, Ray
2019-06-10 2:37 ` Dong, Eric [this message]
2019-06-05 5:49 ` [PATCH v2 2/2] UefiCpuPkg/MpInitLib: Decrease " Ni, Ray
2019-06-10 2:38 ` Dong, Eric
2019-06-05 11:25 ` [edk2-devel] [PATCH v2 0/2] Fix the issue that OS complains memory < 1MB changes across S3 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=ED077930C258884BBCB450DB737E662259E4E78A@shsmsx102.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