[PATCH v2 0/7] ACPI: Add _OST support for ACPI hotplug
From: Toshi Kani
Date: Tue May 08 2012 - 16:15:15 EST
This patchset supports ACPI OSPM Status Indication (_OST) method for
ACPI CPU/memory/container hotplug operations and sysfs eject. After
ACPI hotplug operation has completed, OSPM calls _OST to indicate the
status of the operation to the platform. If _OST is not present, this
patchset has no effect on the platform.
This _OST support can be enabled or disabled with a new config option
CONFIG_ACPI_HOTPLUG_OST. This option is disabled by default. When
this option is disabled, this patchset has no effect on the platform.
The _OST definition can be found in section 6.3.5 of ACPI 5.0 spec.
The HPPF spec below also describes hotplug flows with _OST.
DIG64 Hot-Plug & Partitioning Flow (HPPF) Specification R1.0
The changes have been tested with simulated _OST methods.
- Added CONFIG_ACPI_HOTPLUG_OST option.
- Added _OST support for container hotplug and sysfs eject.
- Reordered patchset to enable _OST support bit of _OSC in the
Toshi Kani (7):
ACPI: Add CONFIG_HOTPLUG_OST option
ACPI: Add an interface to evaluate _OST
ACPI: Add _OST support for sysfs eject
ACPI: Add _OST support for ACPI CPU hotplug
ACPI: Add _OST support for ACPI memory hotplug
ACPI: Add _OST support for ACPI container hotplug
ACPI: Set hotplug _OST support bit to _OSC
drivers/acpi/Kconfig | 14 +++++++++
drivers/acpi/acpi_memhotplug.c | 43 +++++++++++++++++++++-------
drivers/acpi/bus.c | 4 +++
drivers/acpi/container.c | 43 +++++++++++++++++++----------
drivers/acpi/processor_driver.c | 28 +++++++++++++-----
drivers/acpi/scan.c | 58 +++++++++++++++++++++++++++++++++------
drivers/acpi/utils.c | 38 +++++++++++++++++++++++++
include/acpi/acpi_bus.h | 12 +++++++-
include/linux/acpi.h | 31 ++++++++++++++++++++-
9 files changed, 226 insertions(+), 45 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/