2016-05-24 15:39:35 +02:00
|
|
|
/** @file
|
|
|
|
CPU exception handler library implementation for PEIM module.
|
|
|
|
|
2022-05-18 11:51:21 +02:00
|
|
|
Copyright (c) 2016 - 2022, Intel Corporation. All rights reserved.<BR>
|
2019-04-04 01:07:22 +02:00
|
|
|
SPDX-License-Identifier: BSD-2-Clause-Patent
|
2016-05-24 15:39:35 +02:00
|
|
|
|
|
|
|
**/
|
|
|
|
|
|
|
|
#include <PiPei.h>
|
|
|
|
#include "CpuExceptionCommon.h"
|
|
|
|
#include <Library/DebugLib.h>
|
|
|
|
#include <Library/HobLib.h>
|
|
|
|
#include <Library/MemoryAllocationLib.h>
|
2018-09-03 04:36:21 +02:00
|
|
|
#include <Library/PcdLib.h>
|
2016-05-24 15:39:35 +02:00
|
|
|
|
|
|
|
CONST UINTN mDoFarReturnFlag = 0;
|
|
|
|
|
2018-08-31 10:29:20 +02:00
|
|
|
typedef struct {
|
|
|
|
UINT8 ExceptionStubHeader[HOOKAFTER_STUB_SIZE];
|
|
|
|
EXCEPTION_HANDLER_DATA *ExceptionHandlerData;
|
|
|
|
} EXCEPTION0_STUB_HEADER;
|
2016-05-24 15:39:35 +02:00
|
|
|
|
|
|
|
/**
|
2018-08-31 10:29:20 +02:00
|
|
|
Get exception handler data pointer from IDT[0].
|
|
|
|
|
|
|
|
The exception #0 stub header is duplicated in an allocated pool with extra 4-byte/8-byte to store the
|
|
|
|
exception handler data. The new allocated memory layout follows structure EXCEPTION0_STUB_HEADER.
|
|
|
|
The code assumes that all processors uses the same exception handler for #0 exception.
|
2016-05-24 15:39:35 +02:00
|
|
|
|
2017-04-07 04:00:59 +02:00
|
|
|
@return pointer to exception handler data.
|
2016-05-24 15:39:35 +02:00
|
|
|
**/
|
|
|
|
EXCEPTION_HANDLER_DATA *
|
|
|
|
GetExceptionHandlerData (
|
|
|
|
VOID
|
|
|
|
)
|
|
|
|
{
|
2018-08-31 10:29:20 +02:00
|
|
|
IA32_DESCRIPTOR IdtDescriptor;
|
|
|
|
IA32_IDT_GATE_DESCRIPTOR *IdtTable;
|
|
|
|
EXCEPTION0_STUB_HEADER *Exception0StubHeader;
|
|
|
|
|
|
|
|
AsmReadIdtr (&IdtDescriptor);
|
|
|
|
IdtTable = (IA32_IDT_GATE_DESCRIPTOR *)IdtDescriptor.Base;
|
2018-09-07 12:12:46 +02:00
|
|
|
|
2018-08-31 10:29:20 +02:00
|
|
|
Exception0StubHeader = (EXCEPTION0_STUB_HEADER *)ArchGetIdtHandler (&IdtTable[0]);
|
|
|
|
return Exception0StubHeader->ExceptionHandlerData;
|
|
|
|
}
|
2016-05-24 15:39:35 +02:00
|
|
|
|
2018-08-31 10:29:20 +02:00
|
|
|
/**
|
|
|
|
Set exception handler data pointer to IDT[0].
|
|
|
|
|
|
|
|
The exception #0 stub header is duplicated in an allocated pool with extra 4-byte/8-byte to store the
|
|
|
|
exception handler data. The new allocated memory layout follows structure EXCEPTION0_STUB_HEADER.
|
|
|
|
The code assumes that all processors uses the same exception handler for #0 exception.
|
|
|
|
|
2018-09-07 12:12:46 +02:00
|
|
|
@param ExceptionHandlerData pointer to exception handler data.
|
2018-08-31 10:29:20 +02:00
|
|
|
**/
|
|
|
|
VOID
|
|
|
|
SetExceptionHandlerData (
|
|
|
|
IN EXCEPTION_HANDLER_DATA *ExceptionHandlerData
|
|
|
|
)
|
|
|
|
{
|
|
|
|
EXCEPTION0_STUB_HEADER *Exception0StubHeader;
|
|
|
|
IA32_DESCRIPTOR IdtDescriptor;
|
|
|
|
IA32_IDT_GATE_DESCRIPTOR *IdtTable;
|
2021-12-05 23:54:17 +01:00
|
|
|
|
2018-08-31 10:29:20 +02:00
|
|
|
//
|
|
|
|
// Duplicate the exception #0 stub header in pool and cache the ExceptionHandlerData just after the stub header.
|
|
|
|
// So AP can get the ExceptionHandlerData by reading the IDT[0].
|
|
|
|
//
|
|
|
|
AsmReadIdtr (&IdtDescriptor);
|
|
|
|
IdtTable = (IA32_IDT_GATE_DESCRIPTOR *)IdtDescriptor.Base;
|
2018-09-07 12:12:46 +02:00
|
|
|
|
2018-08-31 10:29:20 +02:00
|
|
|
Exception0StubHeader = AllocatePool (sizeof (*Exception0StubHeader));
|
|
|
|
ASSERT (Exception0StubHeader != NULL);
|
|
|
|
CopyMem (
|
|
|
|
Exception0StubHeader->ExceptionStubHeader,
|
|
|
|
(VOID *)ArchGetIdtHandler (&IdtTable[0]),
|
|
|
|
sizeof (Exception0StubHeader->ExceptionStubHeader)
|
|
|
|
);
|
|
|
|
Exception0StubHeader->ExceptionHandlerData = ExceptionHandlerData;
|
|
|
|
ArchUpdateIdtEntry (&IdtTable[0], (UINTN)Exception0StubHeader->ExceptionStubHeader);
|
2016-05-24 15:39:35 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
Common exception handler.
|
|
|
|
|
|
|
|
@param ExceptionType Exception type.
|
|
|
|
@param SystemContext Pointer to EFI_SYSTEM_CONTEXT.
|
|
|
|
**/
|
|
|
|
VOID
|
|
|
|
EFIAPI
|
|
|
|
CommonExceptionHandler (
|
2017-04-07 04:00:59 +02:00
|
|
|
IN EFI_EXCEPTION_TYPE ExceptionType,
|
2016-05-24 15:39:35 +02:00
|
|
|
IN EFI_SYSTEM_CONTEXT SystemContext
|
|
|
|
)
|
|
|
|
{
|
|
|
|
EXCEPTION_HANDLER_DATA *ExceptionHandlerData;
|
|
|
|
|
|
|
|
ExceptionHandlerData = GetExceptionHandlerData ();
|
|
|
|
CommonExceptionHandlerWorker (ExceptionType, SystemContext, ExceptionHandlerData);
|
|
|
|
}
|
|
|
|
|
2022-10-12 09:27:45 +02:00
|
|
|
/**
|
|
|
|
Registers a function to be called from the processor interrupt handler.
|
|
|
|
|
|
|
|
This function registers and enables the handler specified by InterruptHandler for a processor
|
|
|
|
interrupt or exception type specified by InterruptType. If InterruptHandler is NULL, then the
|
|
|
|
handler for the processor interrupt or exception type specified by InterruptType is uninstalled.
|
|
|
|
The installed handler is called once for each processor interrupt or exception.
|
|
|
|
NOTE: This function should be invoked after InitializeCpuExceptionHandlers() is invoked,
|
|
|
|
otherwise EFI_UNSUPPORTED returned.
|
|
|
|
|
|
|
|
@param[in] InterruptType Defines which interrupt or exception to hook.
|
|
|
|
@param[in] InterruptHandler A pointer to a function of type EFI_CPU_INTERRUPT_HANDLER that is called
|
|
|
|
when a processor interrupt occurs. If this parameter is NULL, then the handler
|
|
|
|
will be uninstalled.
|
|
|
|
|
|
|
|
@retval EFI_SUCCESS The handler for the processor interrupt was successfully installed or uninstalled.
|
|
|
|
@retval EFI_ALREADY_STARTED InterruptHandler is not NULL, and a handler for InterruptType was
|
|
|
|
previously installed.
|
|
|
|
@retval EFI_INVALID_PARAMETER InterruptHandler is NULL, and a handler for InterruptType was not
|
|
|
|
previously installed.
|
|
|
|
@retval EFI_UNSUPPORTED The interrupt specified by InterruptType is not supported,
|
|
|
|
or this function is not supported.
|
|
|
|
**/
|
|
|
|
EFI_STATUS
|
|
|
|
EFIAPI
|
|
|
|
RegisterCpuInterruptHandler (
|
|
|
|
IN EFI_EXCEPTION_TYPE InterruptType,
|
|
|
|
IN EFI_CPU_INTERRUPT_HANDLER InterruptHandler
|
|
|
|
)
|
|
|
|
{
|
|
|
|
EXCEPTION_HANDLER_DATA *ExceptionHandlerData;
|
|
|
|
|
|
|
|
ExceptionHandlerData = GetExceptionHandlerData ();
|
|
|
|
return RegisterCpuInterruptHandlerWorker (InterruptType, InterruptHandler, ExceptionHandlerData);
|
|
|
|
}
|
|
|
|
|
2016-05-24 15:39:35 +02:00
|
|
|
/**
|
|
|
|
Initializes all CPU exceptions entries and provides the default exception handlers.
|
2017-04-07 04:00:59 +02:00
|
|
|
|
2016-05-24 15:39:35 +02:00
|
|
|
Caller should try to get an array of interrupt and/or exception vectors that are in use and need to
|
|
|
|
persist by EFI_VECTOR_HANDOFF_INFO defined in PI 1.3 specification.
|
2017-04-07 04:00:59 +02:00
|
|
|
If caller cannot get reserved vector list or it does not exists, set VectorInfo to NULL.
|
2016-05-24 15:39:35 +02:00
|
|
|
If VectorInfo is not NULL, the exception vectors will be initialized per vector attribute accordingly.
|
2017-04-07 04:00:59 +02:00
|
|
|
Note: Before invoking this API, caller must allocate memory for IDT table and load
|
2016-05-24 15:39:35 +02:00
|
|
|
IDTR by AsmWriteIdtr().
|
|
|
|
|
|
|
|
@param[in] VectorInfo Pointer to reserved vector list.
|
2017-04-07 04:00:59 +02:00
|
|
|
|
|
|
|
@retval EFI_SUCCESS CPU Exception Entries have been successfully initialized
|
2016-05-24 15:39:35 +02:00
|
|
|
with default exception handlers.
|
|
|
|
@retval EFI_INVALID_PARAMETER VectorInfo includes the invalid content if VectorInfo is not NULL.
|
|
|
|
@retval EFI_UNSUPPORTED This function is not supported.
|
|
|
|
|
|
|
|
**/
|
|
|
|
EFI_STATUS
|
|
|
|
EFIAPI
|
|
|
|
InitializeCpuExceptionHandlers (
|
|
|
|
IN EFI_VECTOR_HANDOFF_INFO *VectorInfo OPTIONAL
|
|
|
|
)
|
|
|
|
{
|
|
|
|
EFI_STATUS Status;
|
|
|
|
EXCEPTION_HANDLER_DATA *ExceptionHandlerData;
|
|
|
|
RESERVED_VECTORS_DATA *ReservedVectors;
|
|
|
|
|
|
|
|
ReservedVectors = AllocatePool (sizeof (RESERVED_VECTORS_DATA) * CPU_EXCEPTION_NUM);
|
|
|
|
ASSERT (ReservedVectors != NULL);
|
|
|
|
|
|
|
|
ExceptionHandlerData = AllocatePool (sizeof (EXCEPTION_HANDLER_DATA));
|
|
|
|
ASSERT (ExceptionHandlerData != NULL);
|
2022-05-18 11:51:21 +02:00
|
|
|
ExceptionHandlerData->IdtEntryCount = CPU_EXCEPTION_NUM;
|
2016-05-24 15:39:35 +02:00
|
|
|
ExceptionHandlerData->ReservedVectors = ReservedVectors;
|
2022-10-12 09:27:45 +02:00
|
|
|
ExceptionHandlerData->ExternalInterruptHandler = AllocateZeroPool (sizeof (EFI_CPU_INTERRUPT_HANDLER) * ExceptionHandlerData->IdtEntryCount);
|
2016-05-24 15:39:35 +02:00
|
|
|
InitializeSpinLock (&ExceptionHandlerData->DisplayMessageSpinLock);
|
|
|
|
|
|
|
|
Status = InitializeCpuExceptionHandlersWorker (VectorInfo, ExceptionHandlerData);
|
|
|
|
if (EFI_ERROR (Status)) {
|
|
|
|
FreePool (ReservedVectors);
|
|
|
|
FreePool (ExceptionHandlerData);
|
|
|
|
return Status;
|
|
|
|
}
|
|
|
|
|
2018-08-31 10:29:20 +02:00
|
|
|
SetExceptionHandlerData (ExceptionHandlerData);
|
2016-05-24 15:39:35 +02:00
|
|
|
return EFI_SUCCESS;
|
|
|
|
}
|
|
|
|
|
UefiCpuPkg/CpuExceptionHandlerLib: Add stack switch support
If Stack Guard is enabled and there's really a stack overflow happened during
boot, a Page Fault exception will be triggered. Because the stack is out of
usage, the exception handler, which shares the stack with normal UEFI driver,
cannot be executed and cannot dump the processor information.
Without those information, it's very difficult for the BIOS developers locate
the root cause of stack overflow. And without a workable stack, the developer
cannot event use single step to debug the UEFI driver with JTAG debugger.
In order to make sure the exception handler to execute normally after stack
overflow. We need separate stacks for exception handlers in case of unusable
stack.
IA processor allows to switch to a new stack during handling interrupt and
exception. But X64 and IA32 provides different ways to make it. X64 provides
interrupt stack table (IST) to allow maximum 7 different exceptions to have
new stack for its handler. IA32 doesn't have IST mechanism and can only use
task gate to do it since task switch allows to load a new stack through its
task-state segment (TSS).
The new API, InitializeCpuExceptionHandlersEx, is implemented to complete
extra initialization for stack switch of exception handler. Since setting
up stack switch needs allocating new memory for new stack, new GDT table
and task-state segment but the initialization method will be called in
different phases which have no consistent way to reserve those memory, this
new API is allowed to pass the reserved resources to complete the extra
works. This is cannot be done by original InitializeCpuExceptionHandlers.
Considering exception handler initialization for MP situation, this new API
is also necessary, because AP is not supposed to allocate memory. So the
memory needed for stack switch have to be reserved in BSP before waking up
AP and then pass them to InitializeCpuExceptionHandlersEx afterwards.
Since Stack Guard feature is available only for DXE phase at this time, the
new API is fully implemented for DXE only. Other phases implement a dummy
one which just calls InitializeCpuExceptionHandlers().
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
Suggested-by: Ayellet Wolman <ayellet.wolman@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
Reviewed-by: Jeff Fan <vanjeff_919@hotmail.com>
Reviewed-by: Jiewen.yao@intel.com
2017-12-07 13:15:12 +01:00
|
|
|
/**
|
2022-05-20 13:12:35 +02:00
|
|
|
Setup separate stacks for certain exception handlers.
|
2022-08-09 03:25:35 +02:00
|
|
|
If the input Buffer and BufferSize are both NULL, use global variable if possible.
|
UefiCpuPkg/CpuExceptionHandlerLib: Add stack switch support
If Stack Guard is enabled and there's really a stack overflow happened during
boot, a Page Fault exception will be triggered. Because the stack is out of
usage, the exception handler, which shares the stack with normal UEFI driver,
cannot be executed and cannot dump the processor information.
Without those information, it's very difficult for the BIOS developers locate
the root cause of stack overflow. And without a workable stack, the developer
cannot event use single step to debug the UEFI driver with JTAG debugger.
In order to make sure the exception handler to execute normally after stack
overflow. We need separate stacks for exception handlers in case of unusable
stack.
IA processor allows to switch to a new stack during handling interrupt and
exception. But X64 and IA32 provides different ways to make it. X64 provides
interrupt stack table (IST) to allow maximum 7 different exceptions to have
new stack for its handler. IA32 doesn't have IST mechanism and can only use
task gate to do it since task switch allows to load a new stack through its
task-state segment (TSS).
The new API, InitializeCpuExceptionHandlersEx, is implemented to complete
extra initialization for stack switch of exception handler. Since setting
up stack switch needs allocating new memory for new stack, new GDT table
and task-state segment but the initialization method will be called in
different phases which have no consistent way to reserve those memory, this
new API is allowed to pass the reserved resources to complete the extra
works. This is cannot be done by original InitializeCpuExceptionHandlers.
Considering exception handler initialization for MP situation, this new API
is also necessary, because AP is not supposed to allocate memory. So the
memory needed for stack switch have to be reserved in BSP before waking up
AP and then pass them to InitializeCpuExceptionHandlersEx afterwards.
Since Stack Guard feature is available only for DXE phase at this time, the
new API is fully implemented for DXE only. Other phases implement a dummy
one which just calls InitializeCpuExceptionHandlers().
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
Suggested-by: Ayellet Wolman <ayellet.wolman@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
Reviewed-by: Jeff Fan <vanjeff_919@hotmail.com>
Reviewed-by: Jiewen.yao@intel.com
2017-12-07 13:15:12 +01:00
|
|
|
|
2022-08-09 03:25:35 +02:00
|
|
|
@param[in] Buffer Point to buffer used to separate exception stack.
|
|
|
|
@param[in, out] BufferSize On input, it indicates the byte size of Buffer.
|
|
|
|
If the size is not enough, the return status will
|
|
|
|
be EFI_BUFFER_TOO_SMALL, and output BufferSize
|
|
|
|
will be the size it needs.
|
UefiCpuPkg/CpuExceptionHandlerLib: Add stack switch support
If Stack Guard is enabled and there's really a stack overflow happened during
boot, a Page Fault exception will be triggered. Because the stack is out of
usage, the exception handler, which shares the stack with normal UEFI driver,
cannot be executed and cannot dump the processor information.
Without those information, it's very difficult for the BIOS developers locate
the root cause of stack overflow. And without a workable stack, the developer
cannot event use single step to debug the UEFI driver with JTAG debugger.
In order to make sure the exception handler to execute normally after stack
overflow. We need separate stacks for exception handlers in case of unusable
stack.
IA processor allows to switch to a new stack during handling interrupt and
exception. But X64 and IA32 provides different ways to make it. X64 provides
interrupt stack table (IST) to allow maximum 7 different exceptions to have
new stack for its handler. IA32 doesn't have IST mechanism and can only use
task gate to do it since task switch allows to load a new stack through its
task-state segment (TSS).
The new API, InitializeCpuExceptionHandlersEx, is implemented to complete
extra initialization for stack switch of exception handler. Since setting
up stack switch needs allocating new memory for new stack, new GDT table
and task-state segment but the initialization method will be called in
different phases which have no consistent way to reserve those memory, this
new API is allowed to pass the reserved resources to complete the extra
works. This is cannot be done by original InitializeCpuExceptionHandlers.
Considering exception handler initialization for MP situation, this new API
is also necessary, because AP is not supposed to allocate memory. So the
memory needed for stack switch have to be reserved in BSP before waking up
AP and then pass them to InitializeCpuExceptionHandlersEx afterwards.
Since Stack Guard feature is available only for DXE phase at this time, the
new API is fully implemented for DXE only. Other phases implement a dummy
one which just calls InitializeCpuExceptionHandlers().
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
Suggested-by: Ayellet Wolman <ayellet.wolman@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
Reviewed-by: Jeff Fan <vanjeff_919@hotmail.com>
Reviewed-by: Jiewen.yao@intel.com
2017-12-07 13:15:12 +01:00
|
|
|
|
2022-05-20 13:12:35 +02:00
|
|
|
@retval EFI_SUCCESS The stacks are assigned successfully.
|
|
|
|
@retval EFI_UNSUPPORTED This function is not supported.
|
2022-08-09 03:25:35 +02:00
|
|
|
@retval EFI_BUFFER_TOO_SMALL This BufferSize is too small.
|
UefiCpuPkg/CpuExceptionHandlerLib: Add stack switch support
If Stack Guard is enabled and there's really a stack overflow happened during
boot, a Page Fault exception will be triggered. Because the stack is out of
usage, the exception handler, which shares the stack with normal UEFI driver,
cannot be executed and cannot dump the processor information.
Without those information, it's very difficult for the BIOS developers locate
the root cause of stack overflow. And without a workable stack, the developer
cannot event use single step to debug the UEFI driver with JTAG debugger.
In order to make sure the exception handler to execute normally after stack
overflow. We need separate stacks for exception handlers in case of unusable
stack.
IA processor allows to switch to a new stack during handling interrupt and
exception. But X64 and IA32 provides different ways to make it. X64 provides
interrupt stack table (IST) to allow maximum 7 different exceptions to have
new stack for its handler. IA32 doesn't have IST mechanism and can only use
task gate to do it since task switch allows to load a new stack through its
task-state segment (TSS).
The new API, InitializeCpuExceptionHandlersEx, is implemented to complete
extra initialization for stack switch of exception handler. Since setting
up stack switch needs allocating new memory for new stack, new GDT table
and task-state segment but the initialization method will be called in
different phases which have no consistent way to reserve those memory, this
new API is allowed to pass the reserved resources to complete the extra
works. This is cannot be done by original InitializeCpuExceptionHandlers.
Considering exception handler initialization for MP situation, this new API
is also necessary, because AP is not supposed to allocate memory. So the
memory needed for stack switch have to be reserved in BSP before waking up
AP and then pass them to InitializeCpuExceptionHandlersEx afterwards.
Since Stack Guard feature is available only for DXE phase at this time, the
new API is fully implemented for DXE only. Other phases implement a dummy
one which just calls InitializeCpuExceptionHandlers().
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
Suggested-by: Ayellet Wolman <ayellet.wolman@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
Reviewed-by: Jeff Fan <vanjeff_919@hotmail.com>
Reviewed-by: Jiewen.yao@intel.com
2017-12-07 13:15:12 +01:00
|
|
|
**/
|
|
|
|
EFI_STATUS
|
|
|
|
EFIAPI
|
2022-05-20 13:12:35 +02:00
|
|
|
InitializeSeparateExceptionStacks (
|
2022-08-09 03:25:35 +02:00
|
|
|
IN VOID *Buffer,
|
|
|
|
IN OUT UINTN *BufferSize
|
UefiCpuPkg/CpuExceptionHandlerLib: Add stack switch support
If Stack Guard is enabled and there's really a stack overflow happened during
boot, a Page Fault exception will be triggered. Because the stack is out of
usage, the exception handler, which shares the stack with normal UEFI driver,
cannot be executed and cannot dump the processor information.
Without those information, it's very difficult for the BIOS developers locate
the root cause of stack overflow. And without a workable stack, the developer
cannot event use single step to debug the UEFI driver with JTAG debugger.
In order to make sure the exception handler to execute normally after stack
overflow. We need separate stacks for exception handlers in case of unusable
stack.
IA processor allows to switch to a new stack during handling interrupt and
exception. But X64 and IA32 provides different ways to make it. X64 provides
interrupt stack table (IST) to allow maximum 7 different exceptions to have
new stack for its handler. IA32 doesn't have IST mechanism and can only use
task gate to do it since task switch allows to load a new stack through its
task-state segment (TSS).
The new API, InitializeCpuExceptionHandlersEx, is implemented to complete
extra initialization for stack switch of exception handler. Since setting
up stack switch needs allocating new memory for new stack, new GDT table
and task-state segment but the initialization method will be called in
different phases which have no consistent way to reserve those memory, this
new API is allowed to pass the reserved resources to complete the extra
works. This is cannot be done by original InitializeCpuExceptionHandlers.
Considering exception handler initialization for MP situation, this new API
is also necessary, because AP is not supposed to allocate memory. So the
memory needed for stack switch have to be reserved in BSP before waking up
AP and then pass them to InitializeCpuExceptionHandlersEx afterwards.
Since Stack Guard feature is available only for DXE phase at this time, the
new API is fully implemented for DXE only. Other phases implement a dummy
one which just calls InitializeCpuExceptionHandlers().
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
Suggested-by: Ayellet Wolman <ayellet.wolman@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
Reviewed-by: Jeff Fan <vanjeff_919@hotmail.com>
Reviewed-by: Jiewen.yao@intel.com
2017-12-07 13:15:12 +01:00
|
|
|
)
|
|
|
|
{
|
2022-08-09 03:25:35 +02:00
|
|
|
if ((Buffer == NULL) && (BufferSize == NULL)) {
|
2022-05-20 13:12:35 +02:00
|
|
|
return EFI_UNSUPPORTED;
|
2018-09-03 04:36:21 +02:00
|
|
|
}
|
|
|
|
|
2022-08-26 09:04:47 +02:00
|
|
|
return ArchSetupExceptionStack (Buffer, BufferSize);
|
UefiCpuPkg/CpuExceptionHandlerLib: Add stack switch support
If Stack Guard is enabled and there's really a stack overflow happened during
boot, a Page Fault exception will be triggered. Because the stack is out of
usage, the exception handler, which shares the stack with normal UEFI driver,
cannot be executed and cannot dump the processor information.
Without those information, it's very difficult for the BIOS developers locate
the root cause of stack overflow. And without a workable stack, the developer
cannot event use single step to debug the UEFI driver with JTAG debugger.
In order to make sure the exception handler to execute normally after stack
overflow. We need separate stacks for exception handlers in case of unusable
stack.
IA processor allows to switch to a new stack during handling interrupt and
exception. But X64 and IA32 provides different ways to make it. X64 provides
interrupt stack table (IST) to allow maximum 7 different exceptions to have
new stack for its handler. IA32 doesn't have IST mechanism and can only use
task gate to do it since task switch allows to load a new stack through its
task-state segment (TSS).
The new API, InitializeCpuExceptionHandlersEx, is implemented to complete
extra initialization for stack switch of exception handler. Since setting
up stack switch needs allocating new memory for new stack, new GDT table
and task-state segment but the initialization method will be called in
different phases which have no consistent way to reserve those memory, this
new API is allowed to pass the reserved resources to complete the extra
works. This is cannot be done by original InitializeCpuExceptionHandlers.
Considering exception handler initialization for MP situation, this new API
is also necessary, because AP is not supposed to allocate memory. So the
memory needed for stack switch have to be reserved in BSP before waking up
AP and then pass them to InitializeCpuExceptionHandlersEx afterwards.
Since Stack Guard feature is available only for DXE phase at this time, the
new API is fully implemented for DXE only. Other phases implement a dummy
one which just calls InitializeCpuExceptionHandlers().
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Eric Dong <eric.dong@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Michael Kinney <michael.d.kinney@intel.com>
Suggested-by: Ayellet Wolman <ayellet.wolman@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
Reviewed-by: Jeff Fan <vanjeff_919@hotmail.com>
Reviewed-by: Jiewen.yao@intel.com
2017-12-07 13:15:12 +01:00
|
|
|
}
|