Advanced Configuration and Power Interface Specification

ACPI Software Programming Model
Table 5-81 Maximum System Characteristics Table (MSCT) Format
Field
Byte Byte Offset Description
Length
Header
Signature 4 0 ‘MSCT’ Signature for the Maximum System
Characteristics Table.
Length 4 4 Length, in bytes, of the entire MSCT.
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 MSCT, the table ID is the manufacturer model
ID.
OEM Revision 4 24 OEM revision of MSCT for supplied OEM Table ID.
Creator ID 4 28 Vendor ID of utility that created the table. For tables
containing Definition Blocks, this is the ID for the ASL
Compiler.
Creator Revision 4 32 Revision of utility that created the table. For tables
containing Definition Blocks, this is the revision for the
ASL Compiler.
Offset to Proximity
Domain Information
Structure
[OffsetProxDomInfo]
Maximum Number of
Proximity Domains
Maximum Number of
Clock Domains
Maximum Physical
Address
Proximity Domain
Information
Structure[Maximum
Number of Proximity
Domains]
4 36 Offset in bytes to the Proximity Domain Information
Structure table entry.
4 40 Indicates the maximum number of Proximity Domains
ever possible in the system. The number reported in this
field is (maximum domains – 1). For example if there are
0x10000 possible domains in the system, this field
would report 0xFFFF.
4 44 Indicates the maximum number of Clock Domains ever
possible in the system. The number reported in this field
is (maximum domains – 1). See Section 6.2.1, “_CDM
(Clock Domain)”.
8 48 Indicates the maximum Physical Address ever possible
in the system. Note: this is the top of the reachable
physical address.
— [OffsetProx
DomInfo]
A list of Proximity Domain Information for this
implementation. The structure format is defined in the
Maximum Proximity Domain Information Structure
section.
5.2.19.1 Maximum Proximity Domain Information Structure
The Maximum Proximity Domain Information Structure is used to report system maximum
characteristics. It is likely that these characteristics may be the same for many proximity domains,
but they can vary from one proximity domain to another. This structure optimizes to cover the
Version 6.0 165