Message ID | 20231113201236.30668-1-salil.mehta@huawei.com (mailing list archive) |
---|---|
Headers | show |
Series | Add architecture agnostic code to support vCPU Hotplug | expand |
On Mon, 13 Nov 2023 20:12:28 +0000 Salil Mehta <salil.mehta@huawei.com> wrote: [...] > physmem: Add helper function to destroy CPU AddressSpace > gdbstub: Add helper function to unregister GDB register space [...] above patches look like potential bugfixes (modulo they aren't getting used actually), only commit messages do not mention adverse effects (which they should do). Question is: do un-destroyed/registered CPU AS and GDB RS affect machines that already support cpu hot-unplug? (x86/s380/spapr)
On Mon, 13 Nov 2023 20:12:28 +0000 Salil Mehta <salil.mehta@huawei.com> wrote: > Virtual CPU hotplug support is being added across various architectures[1][3]. > This series adds various code bits common across all architectures: > > 1. vCPU creation and Parking code refactor [Patch 1] > 2. Update ACPI GED framework to support vCPU Hotplug [Patch 2,3] > 3. ACPI CPUs AML code change [Patch 4,5] > 4. Helper functions to support unrealization of CPU objects [Patch 6,7] > 5. Docs [Patch 8] [...] forgot to mention, you probably need to add to series migration code as well as it should be the same for both targets. (mostly copy-paste from q35 or piix4 and making sure it doesn't break old qemu (aka not enabled/sent over wire if cpu hotplug event is disabled))