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
| ||
|
Date: Mon, 16 Jul 2012 08:52:07 -0400 From: Prarit Bhargava <prarit@...hat.com> To: "Kani, Toshimitsu" <toshi.kani@...com> CC: "lenb@...nel.org" <lenb@...nel.org>, "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, "bhelgaas@...gle.com" <bhelgaas@...gle.com>, "shuahkhan@...il.com" <shuahkhan@...il.com>, "liuj97@...il.com" <liuj97@...il.com>, "andi@...stfloor.org" <andi@...stfloor.org>, "isimatu.yasuaki@...fujitsu.com" <isimatu.yasuaki@...fujitsu.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v6 0/6] ACPI: Add _OST support for ACPI hotplug On 01/-10/-28163 02:59 PM, Kani, Toshimitsu wrote: > * This version updates to use pr_<level> over printk to accommodate > checkpatch update since this patchset was accepted in -next. > > This patchset supports ACPI OSPM Status Indication (_OST) method for > ACPI CPU/memory/container hotplug operations and sysfs eject. After > an ACPI hotplug operation has completed, OSPM calls _OST to indicate > the result of the operation to the platform. If a platform does not > support _OST, this patchset has no effect on the platform. > > This _OST support is enabled when all relevant ACPI hotplug operations, > such as CPU, memory and container hotplug, are enabled. This assures > consistent behavior among the hotplug operations with regarding the > _OST support. > > Some platforms may require the OS to support _OST in order to support > ACPI hotplug operations. For example, if a platform has the management > console where user can request a hotplug operation from, this _OST > support would be required for the management console to show the result > of the hotplug request to user. > > 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 changes have been tested with simulated _OST methods. > > v6: > - Updated to use pr_<level> over printk. > > v5: > - Updated change log in patch 5/6. > > v4: > - Removed CONFIG_ACPI_HOTPLUG_OST option. > > v3: > - Added more descriptions to the change logs. > > v2: > - 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 > last patch. > > --- > Toshi Kani (6): > 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 I have a few systems on which I can do some _OST CPU and Memory hotplug. These systems are newer Intel systems in which ACPI events can be triggered via switches to add CPUs. I tested this patchset with CPU _add_ and haven't seen any issues. So... Tested-by: Prarit Bhargava <prarit@...hat.com> P. -- 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