![Intel ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS VOLUME 3 REV 2.3 Manual Download Page 530](http://html.mh-extra.com/html/intel/itanium-architecture-software-developers-volume-3-rev-2-3/itanium-architecture-software-developers-volume-3-rev-2-3_manual_2073404530.webp)
2:282
Volume 2, Part 1: Processor Abstraction Layer
11.1.3
PAL Entrypoints
The following hardware events can trigger the execution of a PAL entrypoint:
• Power-on/reset
• Hardware errors (both correctable and uncorrectable)
• Initialization event (via external interrupt bus message or processor pin)
• Platform management interrupt (via external interrupt bus message or processor
pin)
These hardware events trigger the execution of one of the following PAL entrypoints (as
shown in
Figure 11-2
):
• PALE_RESET
–
Initializes and tests the processor following power-on or reset and
then branches to SALE_ENTRY to determine whether to perform firmware recovery
update, or to boot the machine for OS use. See
Section 11.1.4, “SAL Entrypoints”
.
• PALE_CHECK
–
Determines if errors are processor related, saves processor related
error information and corrects errors where possible (for example, by flushing a
corrupted instruction cache line and marking the cache line as unusable). In all
cases, PALE_CHECK branches to SALE_ENTRY to complete the error logging,
correction, and reporting.
• PALE_INIT
–
Saves the processor state, places the processor in a known state, and
branches to SALE_ENTRY. PALE_INIT is entered as a response to an initialization
event.
• PALE_PMI
–
Saves the processor state and branches to SALE_PMI. PALE_PMI is
entered as a response to a platform management interrupt.
11.1.4
SAL Entrypoints
There are two entrypoints from PAL into SAL:
• SALE_ENTRY
–
PAL branches to this SAL entrypoint after a power-on, reset,
machine check, or initialization event. If SALE_ENTRY was invoked by a machine
check or initialization event, SALE_ENTRY branches to the appropriate routine:
• SAL_CHECK is invoked after a machine check.
• SAL_INIT is invoked after an initialization event.
If SALE_ENTRY was invoked by a reset or power on, it checks to determine if a
firmware recovery condition exists. If it does, SALE_ENTRY performs the firmware
update, then performs a RESET operation to invoke PAL_RESET. If a recovery
condition does not exist, SAL_ENTRY returns to PAL_RESET to complete processor
self-test. PAL_RESET then branches back to SALE_ENTRY, which, in turn, branches
to SAL_RESET.
• SALE_PMI
–
platform management interrupt. PALE_PMI branches to this SAL
entrypoint after saving processor state in response to the platform management
interrupt.
Summary of Contents for ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS VOLUME 3 REV 2.3
Page 1: ......
Page 11: ...x Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 13: ...1 2 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 33: ...1 22 Volume 1 Part 1 Introduction to the Intel Itanium Architecture ...
Page 57: ...1 46 Volume 1 Part 1 Execution Environment ...
Page 147: ...1 136 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 149: ...1 138 Volume 1 Part 2 About the Optimization Guide ...
Page 191: ...1 180 Volume 1 Part 2 Predication Control Flow and Instruction Stream ...
Page 230: ......
Page 248: ...236 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 250: ...2 2 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 264: ...2 16 Volume 2 Part 1 Intel Itanium System Environment ...
Page 380: ...2 132 Volume 2 Part 1 Interruptions ...
Page 398: ...2 150 Volume 2 Part 1 Register Stack Engine ...
Page 486: ...2 238 Volume 2 Part 1 IA 32 Interruption Vector Descriptions ...
Page 750: ...2 502 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 754: ...2 506 Volume 2 Part 2 About the System Programmer s Guide ...
Page 796: ...2 548 Volume 2 Part 2 Interruptions and Serialization ...
Page 808: ...2 560 Volume 2 Part 2 Context Management ...
Page 842: ...2 594 Volume 2 Part 2 Floating point System Software ...
Page 850: ...2 602 Volume 2 Part 2 IA 32 Application Support ...
Page 862: ...2 614 Volume 2 Part 2 External Interrupt Architecture ...
Page 870: ...2 622 Volume 2 Part 2 Performance Monitoring Support ...
Page 891: ......
Page 1099: ...3 200 Volume 3 Instruction Reference padd Interruptions Illegal Operation fault ...
Page 1295: ...3 396 Volume 3 Resource and Dependency Semantics ...
Page 1296: ......
Page 1302: ...402 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 1494: ...4 192 Volume 4 Base IA 32 Instruction Reference FWAIT Wait See entry for WAIT ...
Page 1647: ...Volume 4 Base IA 32 Instruction Reference 4 345 ROL ROR Rotate See entry for RCL RCR ROL ROR ...
Page 1884: ...4 582 Volume 4 IA 32 SSE Instruction Reference ...
Page 1885: ...Index Intel Itanium Architecture Software Developer s Manual Rev 2 3 Index ...
Page 1886: ...Index Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 1898: ...INDEX Index 12 Index for Volumes 1 2 3 and 4 ...