Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification
Field
Signature 4 0 ‘CPEP’. Signature for the Corrected Platform Error Polling Table.
Length 4 4 Length, in bytes, of the entire CPET. The length implies the
number of Entry fields at the end of the table
Revision 1 8 1
Checksum 1 9 Entire table must sum to zero.
OEMID 6 10 OEM ID.
OEM Table ID 8 16 For the Corrected Platform Error Polling Table, the table ID is the
manufacturer model ID.
OEM Revision 4 24 OEM revision of Corrected Platform Error Polling Table for
supplied OEM Table ID.
Creator ID 4 28 Vendor ID of utility that created the table.
Creator Revision 4 32 Revision of utility that created the table.
Reserved 8 36 Reserved, must be 0.
CPEP Processor
Structure[n]
Byte
Length
Byte
Offset
Description
--- 44 A list of Corrected Platform Error Polling Processor structures for
the platform. See Section 5.2.18.1,” Corrected Platform Error
Polling Processor Structure”.
5.2.18.1 Corrected Platform Error Polling Processor Structure
The Corrected Platform Error Polling Processor structure provides information on the specific
processors OSPM polls for error information. Table 5-80 provides the details of the Corrected
Platform Error Polling Processor structure.
Table 5-80 Corrected Platform Error Polling Processor Structure
Field
Byte
Length
Byte
Offset
Description
Type 1 0 0 Corrected Platform Error Polling Processor structure for
APIC/SAPIC based processors
Length 1 1 8
Processor ID 1 2 Processor ID of destination.
Processor EID 1 3 Processor EID of destination.
Polling Interval 4 4 Platform-suggested polling interval (in milliseconds)
5.2.19 Maximum System Characteristics Table (MSCT)
This section describes the format of the Maximum System Characteristic Table (MSCT), which
provides OSPM with information characteristics of a system’s maximum topology capabilities. If
the system maximum topology is not known up front at boot time, then this table is not present.
OSPM will use information provided by the MSCT only when the System Resource Affinity Table
(SRAT) exists. The MSCT must contain all proximity and clock domains defined in the SRAT.
164 April, 2015 Version 6.0