From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Fan, Jeff" <jeff.fan@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [PATCH v2 0/3] Put AP into safe hlt-loop code on S3 path
Date: Tue, 15 Nov 2016 01:21:49 +0000 [thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C50386D0C34@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <542CF652F8836A4AB8DBFAAD40ED192A4A2DCDE3@shsmsx102.ccr.corp.intel.com>
HI jeff
The patch looks good and I have one minor suggestion on below comment:
Allocate safe memory in ACPI NVS for AP to execute hlt loop on S3 path
==>
Allocate safe memory in ACPI NVS for AP to execute hlt loop in protected mode on S3 path
I recommend we add "in protected mode" statement for the reason to allocate below 4GiB memory.
With that comment update, reviewed-by: Jiewen.yao@intel.com
Thank you
Yao Jiewen
> -----Original Message-----
> From: Fan, Jeff
> Sent: Tuesday, November 15, 2016 8:50 AM
> To: Yao, Jiewen <jiewen.yao@intel.com>
> Subject: FW: [edk2] [PATCH v2 0/3] Put AP into safe hlt-loop code on S3 path
>
>
>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Jeff Fan
> Sent: Friday, November 11, 2016 1:46 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH v2 0/3] Put AP into safe hlt-loop code on S3 path
>
> On S3 path, we will wake up APs to restore CPU context in
> PiSmmCpuDxeSmm
> driver. In case, one NMI or SMI happens, APs may exit from hlt state and
> execute the instruction after HLT instruction.
>
> But APs are not running on safe code, it leads OVMF S3 boot unstable.
>
> https://bugzilla.tianocore.org/show_bug.cgi?id=216
>
> I tested real platform with 64bit DXE.
>
> v2:
> 1. Make stack alignment per Laszlo's comment.
> 2. Trim whitespace at end of end per Laszlo's comment.
> 3. Update year mark in file header.
> 4. Enhancement on InterlockedDecrement() per Paolo's comment.
>
> Jeff Fan (3):
> UefiCpuPkg/PiSmmCpuDxeSmm: Put AP into safe hlt-loop code on S3 path
> UefiCpuPkg/PiSmmCpuDxeSmm: Place AP to 32bit protected mode on S3
> path
> UefiCpuPkg/PiSmmCpuDxeSmm: Decrease mNumberToFinish in AP safe
> code
>
> UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c | 33
> +++++++++++++-
> UefiCpuPkg/PiSmmCpuDxeSmm/Ia32/SmmFuncsArch.c | 29 +++++++++++-
> UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h | 15 +++++++
> UefiCpuPkg/PiSmmCpuDxeSmm/X64/SmmFuncsArch.c | 63
> ++++++++++++++++++++++++++-
> 4 files changed, 136 insertions(+), 4 deletions(-)
>
> --
> 2.9.3.windows.2
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-11-15 1:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 5:45 [PATCH v2 0/3] Put AP into safe hlt-loop code on S3 path Jeff Fan
2016-11-11 5:45 ` [PATCH v2 1/3] UefiCpuPkg/PiSmmCpuDxeSmm: " Jeff Fan
2016-11-11 5:45 ` [PATCH v2 2/3] UefiCpuPkg/PiSmmCpuDxeSmm: Place AP to 32bit protected mode " Jeff Fan
2016-11-11 5:45 ` [PATCH v2 3/3] UefiCpuPkg/PiSmmCpuDxeSmm: Decrease mNumberToFinish in AP safe code Jeff Fan
2016-11-11 10:16 ` Paolo Bonzini
2016-11-11 19:49 ` [PATCH v2 0/3] Put AP into safe hlt-loop code on S3 path Laszlo Ersek
2016-11-13 12:51 ` Fan, Jeff
2016-11-14 1:41 ` Yao, Jiewen
2016-11-14 8:17 ` Laszlo Ersek
2016-11-14 8:50 ` Paolo Bonzini
2016-11-14 10:39 ` Laszlo Ersek
2016-11-14 11:09 ` Paolo Bonzini
2016-11-14 11:27 ` Laszlo Ersek
2016-11-14 12:00 ` Paolo Bonzini
2016-11-14 18:07 ` Laszlo Ersek
2016-11-14 18:13 ` Paolo Bonzini
2016-11-14 23:56 ` Laszlo Ersek
2016-11-15 0:47 ` Fan, Jeff
2016-11-15 1:03 ` Laszlo Ersek
2016-11-15 1:04 ` Fan, Jeff
2016-11-15 1:19 ` Fan, Jeff
2016-11-15 1:30 ` Laszlo Ersek
2016-11-15 1:27 ` Laszlo Ersek
2016-11-15 1:38 ` Fan, Jeff
[not found] ` <542CF652F8836A4AB8DBFAAD40ED192A4A2DCDE3@shsmsx102.ccr.corp.intel.com>
2016-11-15 1:21 ` Yao, Jiewen [this message]
2016-11-15 1:24 ` Fan, Jeff
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=74D8A39837DF1E4DA445A8C0B3885C50386D0C34@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