Review: acpi processor hotplug
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest15 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/15 | Make a GPE register block be acessible.bios/ | +2 | 0 replies | |
| 2/15 | mark extra cpus as presentbios/ bios/ | +15 | 0 replies | |
| 3/15 | introduce cpu_set to qemu monitorqemu/ qemu/ qemu/ | +22 | 1 reply | |
| 4/15 | mark processors as presentsbios/ | +19 | 4 replies | |
| 5/15 | provide gpe _L0x methodsbios/ | +51 | 0 replies | |
| 6/15 | provide operation region for pio to the gpesbios/ | +7 | 0 replies | |
| 7/15 | implement method _L00 for GPE0bios/ | +114 | 0 replies | |
| 8/15 | isolate cpu initialization function in hw/pc.cqemu/ qemu/ | +24 | 0 replies | |
| 9/15 | initialize hot add system.qemu/ qemu/ | +36 | 0 replies | |
| 10/15 | handle gpe data for pioqemu/ | +36 | 0 replies | |
| 11/15 | manipulate the gpe bits and send sci up the os.qemu/ | +42 | 0 replies | |
| 12/15 | isolate cpu thread creation in qemu-kvm.cqemu/ qemu/ | +8 | 0 replies | |
| 13/15 | provide _MAT to acpi processorbios/ | +140 | 0 replies | |
| 14/15 | start a new cpu threadqemu/ | +16 | 0 replies | |
| 15/15 | provide _EJ0 method for processor removalbios/ qemu/ | +14 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/15] Review: acpi processor hotplug
Hi,
In this series, I'm sending the result-so-far of my work with acpi for processor hotplug. I'm able to put a cpu up and down (with the help of some udev scripts I wrote), but it still has some known bugs and issues. For x86_64 linux machines (because the kernel supports it), you can plug cpus that _were not_ listed initially in smp_cpus.
The usage is : cpu_set x (online/offline), in qemu monitor. It will then send the proper signals to the cpu #x.
However, it is important to note that:
* there's no way to know if it suceeded. (ex, if the udev scripts are not running, the cpu will not be put up, and you'll never know)
* there's no way to unconditionally send an add signal. (if you send BUS_CHECK again, and the cpu is already marked as present, it will offline it instead)
because of that, management gets a bit complicated. The ideal situation is to specify:
"I want Y cpus", and have it. Error reported in case it fails. Because of that, I _still_ advocate for an alternative virtio implementation. ACPI still plays its role in this scenario, but not the full role.
In my TODO list, you'll find:
* fix some more issues in this code, and merge the gently comments I'm sure you'll make
* device acpi hotplug
* virtio cpu hotplug for linux (meaning refactoring the existing patch)
* occupy 24 territories.
* conquer 18 territories with at least 2 battalions on each.
Besides a bunch of boring personal items I'm sure are not of interest to anybody here.
Thanks in advance
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/