lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Apr 2012 16:21:46 -0600
From:	Toshi Kani <toshi.kani@...com>
To:	lenb@...nel.org, linux-acpi@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, Toshi Kani <toshi.kani@...com>
Subject: [PATCH 0/5] ACPI: Add _OST support for ACPI hotplug

This series of patches supports ACPI _OST (OSPM Status Indication)
method for ACPI-based CPU and memory hotplug operations.  After
ACPI-based hotplug operation completed, OSPM calls _OST to convey
the completion status to ACPI firmware.  If _OST is not present,
this change 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
  http://www.dig64.org/home/DIG64_HPPF_R1_0.pdf

The change was tested by overriding DSDT with fake _OST methods.

---
Toshi Kani (4):
 ACPI: Set hotplug _OST support bit to _OSC
 ACPI: Add acpi_evaluate_ost() for calling _OST
 ACPI: Add _OST support for ACPI CPU hotplug
 ACPI: Add _OST support for ACPI memory hotplug

 drivers/acpi/acpi_memhotplug.c  |   43 +++++++++++++++++++++++++++++----------
 drivers/acpi/bus.c              |    5 ++++
 drivers/acpi/processor_driver.c |   28 ++++++++++++++++++-------
 drivers/acpi/utils.c            |   34 ++++++++++++++++++++++++++++++
 include/acpi/acpi_bus.h         |    3 ++
 include/linux/acpi.h            |   26 ++++++++++++++++++++++-
 6 files changed, 119 insertions(+), 20 deletions(-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ