[PATCH part3 0/5] acpi, acpica: Initialize acpi_gbl_root_table_list earlier and override it later.

From: Tang Chen
Date: Thu Aug 08 2013 - 04:55:42 EST


In order to prevent bootmem allocator (memblock) from allocating hotpluggable
memory for the kernel, we need to obtain SRAT earlier.

In part1 patch-set, we have split acpi_gbl_root_table_list initialization into
two steps: install and override.

This patch-set will do install step earlier. This will help us to find SRAT provided
by firmware earlier in later patches.

The current kernel looks like this:

setup_arch()
|->acpi_initrd_override() /* Find all tables specified by users in initrd,
| and store them in acpi_tables_addr array. */
|......
|->acpi_boot_table_init() /* Find all tables in firmware and install them
into acpi_gbl_root_table_list. Check acpi_tables_addr,
if any table needs to be overrided, override it. */

After this patch-set, the kernel will look like this:

setup_arch()
|->early_acpi_boot_table_init() /* Find all tables in firmware and install them
| into acpi_gbl_root_table_list. No override. */
|
|->acpi_initrd_override() /* Find all tables specified by users in initrd,
| and store them in acpi_tables_addr array. */
|......
|->acpi_boot_table_init() /* Check acpi_tables_addr, if any table needs to
be overrided, override it. */


Tang Chen (5):
x86, acpi: Call two new functions instead of acpi_initialize_tables()
in acpi_table_init().
x86, acpi: Split acpi_table_init() into two parts.
x86, acpi: Rename check_multiple_madt() and make it global.
x86, acpi: Split acpi_boot_table_init() into two parts.
x86, acpi: Initialize acpi golbal root table list earlier.

arch/x86/kernel/acpi/boot.c | 32 ++++++++++++++++++++------------
arch/x86/kernel/setup.c | 8 +++++++-
drivers/acpi/tables.c | 29 +++++++++++++++++++++++------
include/acpi/acpixf.h | 4 ++++
include/linux/acpi.h | 4 ++++
5 files changed, 58 insertions(+), 19 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/