From: Jeff Fan <jeff.fan@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH 0/3] Display new stack base and size
Date: Fri, 4 Nov 2016 10:18:59 +0800 [thread overview]
Message-ID: <20161104021902.17364-1-jeff.fan@intel.com> (raw)
Dump new stack base and size could help developer to fix stack crash
issue.
Normally, stack is changed by EnablePaging64()/DisablePaging64()/SwitchStack().
But these APIs have no knowledge of stack size. It's better to let caller
display the stack base and size informations. Some modules alreadys displayed
stack information. This serial of patches are to fix those modules missing it.
We also fixed one bug in DxeIplPeim, local BaseOfStack is overwritten wrongly.
https://bugzilla.tianocore.org/show_bug.cgi?id=186
Jeff Fan (3):
MdeModulePkg: Display new stack base and size
UefiCpuPkg: Display new stack base and size
MdeModulePkg/DxeIplPeim: UINTN used wrongly for EFI_PHYSICAL_ADDRESS
MdeModulePkg/Core/DxeIplPeim/Ia32/DxeLoadFunc.c | 19 ++++++++++++++++++-
MdeModulePkg/Universal/CapsulePei/UefiCapsule.c | 8 ++++++++
MdeModulePkg/Universal/CapsulePei/X64/X64Entry.c | 8 ++++++++
UefiCpuPkg/SecCore/SecMain.c | 10 +++++++++-
UefiCpuPkg/Universal/Acpi/S3Resume2Pei/S3Resume.c | 7 +++++++
5 files changed, 50 insertions(+), 2 deletions(-)
--
2.9.3.windows.2
next reply other threads:[~2016-11-04 2:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 2:18 Jeff Fan [this message]
2016-11-04 2:19 ` [PATCH 1/3] MdeModulePkg: Display new stack base and size Jeff Fan
2016-11-04 2:19 ` [PATCH 2/3] UefiCpuPkg: " Jeff Fan
2016-11-04 2:19 ` [PATCH 3/3] MdeModulePkg/DxeIplPeim: UINTN used wrongly for EFI_PHYSICAL_ADDRESS Jeff Fan
2016-11-04 3:28 ` Gao, Liming
2016-11-04 4:49 ` Gao, Liming
2016-11-09 7:21 ` [PATCH 0/3] Display new stack base and size Tian, Feng
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=20161104021902.17364-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