From: Jeff Fan <jeff.fan@intel.com>
To: edk2-devel@lists.01.org
Cc: Laszlo Ersek <lersek@redhat.com>, Feng Tian <feng.tian@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: [PATCH 0/3] UefiCpuPkg/DxeMpLib: Allocate new safe stack < 4GB
Date: Wed, 23 Nov 2016 22:01:35 +0800 [thread overview]
Message-ID: <20161123140138.15976-1-jeff.fan@intel.com> (raw)
Allocate safe AP stack under 4GB and make sure BSP wait till all APs running in
safe code.
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Feng Tian <feng.tian@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jeff Fan <jeff.fan@intel.com>
Jeff Fan (3):
UefiCpuPkg/DxeMpLib: Get safe AP loop handler from global variable
UefiCpuPkg/DxeMpLib: Allocate new safe stack < 4GB
UefiCpuPkg/DxeMpLib: Make sure APs in safe loop code
UefiCpuPkg/Library/MpInitLib/DxeMpLib.c | 29 ++++++++++++++++++++++----
UefiCpuPkg/Library/MpInitLib/Ia32/MpFuncs.nasm | 11 ++++++++--
UefiCpuPkg/Library/MpInitLib/MpLib.h | 4 +++-
UefiCpuPkg/Library/MpInitLib/X64/MpFuncs.nasm | 5 +++++
4 files changed, 42 insertions(+), 7 deletions(-)
--
2.9.3.windows.2
next reply other threads:[~2016-11-23 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 14:01 Jeff Fan [this message]
2016-11-23 14:01 ` [PATCH 1/3] UefiCpuPkg/DxeMpLib: Get safe AP loop handler from global variable Jeff Fan
2016-11-23 17:08 ` Laszlo Ersek
2016-11-23 14:01 ` [PATCH 2/3] UefiCpuPkg/DxeMpLib: Allocate new safe stack < 4GB Jeff Fan
2016-11-23 18:31 ` Laszlo Ersek
2016-11-24 2:23 ` Fan, Jeff
2016-11-24 9:20 ` Laszlo Ersek
2016-11-24 13:48 ` Fan, Jeff
2016-11-24 21:13 ` Laszlo Ersek
2016-11-23 14:01 ` [PATCH 3/3] UefiCpuPkg/DxeMpLib: Make sure APs in safe loop code Jeff Fan
2016-11-23 18:52 ` Laszlo Ersek
2016-11-24 2:37 ` 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=20161123140138.15976-1-jeff.fan@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