Add per-table execution of module-level code, early region handlers

1) Execute any module-level code after each ACPI table (DSDT or SSDT)
is loaded into the namespace (rather than after all AML tables have
been loaded. This matches the behavior of other ACPI
implementations and is required to support BIOS code that
depends on this behavior.

2) Install default operation region handlers for the "basic"
address spaces - Memory, I/O, and PCI_Config. Not only are these
spaces required to be "always available" by the ACPI specification,
these handlers are required in order to execute the module-level
code described in (1). This will support BIOS code that depends
on these operation regions.

1 files changed, 6 insertions, 0 deletions

diff --git a/source/components/events/evregion.c b/source/components/events/evregion.c
index 2b006160f..e9dbb7ff4 100644
--- a/source/components/events/evregion.c
+++ b/source/components/events/evregion.c
@@ -210,6 +210,12 @@ AcpiEvInitializeOpRegions (
  * DESCRIPTION: Dispatch an address space or operation region access to
  *              a previously installed handler.
  *
+ * NOTE: During early initialization, we always install the default region
+ * handlers for Memory, I/O and PCI_Config. This ensures that these operation
+ * region address spaces are always available as per the ACPI specification.
+ * This is especially needed in order to support the execution of
+ * module-level AML code during loading of the ACPI tables.
+ *
  ******************************************************************************/
 
 ACPI_STATUS