From: "Zhiguang Liu" <zhiguang.liu@intel.com>
To: devel@edk2.groups.io
Cc: Zhiguang Liu <zhiguang.liu@intel.com>,
Eric Dong <eric.dong@intel.com>, Ray Ni <ray.ni@intel.com>,
Rahul Kumar <rahul1.kumar@intel.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Dandan Bi <dandan.bi@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Jian J Wang <jian.j.wang@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: [PATCH 0/2] Simplify InitializeSeparateExceptionStacks
Date: Fri, 22 Jul 2022 15:57:35 +0800 [thread overview]
Message-ID: <20220722075737.897-1-zhiguang.liu@intel.com> (raw)
The patch set is to hide the exception implementation details, so that
caller don't need to know anything about IDT when separate stack for it.
However, this patch set changes a library API, so I have to change
multiple packages inside one patch. Otherwise, I can make sure every
single commit can build and boot fine. If anyone has good idea to separate
the first big patch, please tell me. Thanks in advance.
Cc: Eric Dong <eric.dong@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: Rahul Kumar <rahul1.kumar@intel.com>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: Dandan Bi <dandan.bi@intel.com>
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Jian J Wang <jian.j.wang@intel.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Sami Mujawar <sami.mujawar@arm.com>
Signed-off-by: Zhiguang Liu <zhiguang.liu@intel.com>
Zhiguang Liu (2):
UefiCpuPkg: Simplify InitializeSeparateExceptionStacks
MdeModulePkg: Move CPU_EXCEPTION_INIT_DATA to UefiCpuPkg
.../Library/ArmExceptionLib/ArmExceptionLib.c | 15 +-
MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c | 4 +-
.../Include/Library/CpuExceptionHandlerLib.h | 82 +--------
.../CpuExceptionHandlerLibNull.c | 15 +-
UefiCpuPkg/CpuDxe/CpuMp.c | 157 +++-------------
UefiCpuPkg/CpuDxe/CpuMp.h | 10 +-
UefiCpuPkg/CpuMpPei/CpuMpPei.c | 174 ++++--------------
UefiCpuPkg/CpuMpPei/CpuMpPei.h | 10 +-
.../CpuExceptionCommon.h | 59 +++++-
.../CpuExceptionHandlerLib/DxeException.c | 77 +++++---
.../Ia32/ArchExceptionHandler.c | 3 +-
.../CpuExceptionHandlerLib/PeiCpuException.c | 62 ++++++-
.../PeiCpuExceptionHandlerLib.inf | 4 +-
.../SecPeiCpuException.c | 15 +-
.../CpuExceptionHandlerLib/SmmException.c | 15 +-
.../X64/ArchExceptionHandler.c | 3 +-
16 files changed, 289 insertions(+), 416 deletions(-)
--
2.26.2.windows.1
next reply other threads:[~2022-07-22 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 7:57 Zhiguang Liu [this message]
2022-07-22 7:57 ` [PATCH 1/2] UefiCpuPkg: Simplify InitializeSeparateExceptionStacks Zhiguang Liu
2022-07-22 10:48 ` Sami Mujawar
2022-08-04 5:37 ` Ni, Ray
2022-07-22 7:57 ` [PATCH 2/2] MdeModulePkg: Move CPU_EXCEPTION_INIT_DATA to UefiCpuPkg Zhiguang Liu
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=20220722075737.897-1-zhiguang.liu@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