@page { size: 21cm 29.7cm; margin: 2cm }
P { margin-bottom: 0.21cm }
H3 { margin-bottom: 0.21cm }
H3.western { font-family: "文鼎PL中楷Uni", serif }
H3.cjk { font-family: "文鼎PL细上海宋Uni"; font-style: normal }
H3.ctl { font-family: "文鼎PL细上海宋Uni" }
-->bibliography:
http://www.books24x7.com/book/id_6137/viewer.asp?bookid=6137&chunkid=0441939724
The
Root System Description Table (RSDT) is the directory to all the
other description tables, providing the operating system access to
all the available ACPI data
RSDT
is stored in the last 64KB below TOM.
Fixed
ACPI Description Table (FADT)
Data
in the FADT includes fixed-length entries describing the fixed ACPI
features of the hardware
It
also has the physical addresses of the Differentiated System
Description Table (DSDT) and Firmware ACPI Control Structure (FACS)
Differentiated
System Description Table (DSDT)
Differentiated
Definition Block that contains implementation and configuration
information beyond what's in the ACPI hardware registers the OSPM
uses for power management, thermal management,
or Plug and Play.
DSDT
is a required table located at offset 0 in the segment from TOM-128K
to TOM-64K
(TOM
= top of memory)
RSDT-->
FADT --> DSDT
SSDT—Secondary
System Description Table
PSDT—Persistent
System Description Table
The
PSDT has been removed from the ACPI 2.0 specification
MADT—Multiple
APIC Description Table
FACS—Firmware
ACPI Control Structure
The
FACS contains the system’s hardware signature
at last boot, the firmware waking vector,
and the global lock
When
the system boots, OSPM uses the E820 BIOS call to obtain a system
memory map
The
BIOS should decide where the different memory structures belong and
configure the E820 handler to return the appropriate values
For
this example, the BIOS reports the system memory map by E820 as
shown: Figure 1
The
BIOS has set aside memory from the Top of Memory1 to Top of Memory2
as ACPI NVS Memory and Reserved Memory,
and has marked both as reserved. A legacy operating system throws out
the ACPI NVS Memory and marks this area
as reserved memory, preventing the memory range from being allocated
to any add-in device.
Operating
System Loading
To see Figure 2
