On Mon, 7 Jul 2025 at 18:53, Michael S. Tsirkin <m...@redhat.com> wrote: > > On Mon, Jul 07, 2025 at 07:09:34PM +0200, Eric Auger wrote: > > Hi, > > > > On 7/3/25 2:35 PM, Eric Auger wrote: > > > This series enables ACPI PCI hotplug/hotunplug on ARM. > > > It is not enabled by default and ACPI PCI hotplug can > > > be selected by setting: > > > > > > -global acpi-ged.acpi-pci-hotplug-with-bridge-support=on > > > > > > Expected benefits should be similar to those listed in [1], > > > ie. removal of some racy behaviors, improved latencies. > > > > > > The infrastructure used in x86 is heavily reused and a > > > huge part of the series consists in moving code from > > > hw/i386/acpi-build.c to a generic place and slightly > > > adapting it to make it usable on ARM. The DSDT table is > > > augmented to support ACPI PCI hotplug elements. > > > > > > On ARM we use use a GED event to notify the OS about > > > hotplug events. > > > > gentle ping on this series. I was hoping that this could target 10.1 but > > I ackowledge this is a big series to review and I am already very > > grateful to all reviewers. > > > > At least patches 1-15 have collected R-bs including Igor's ones. They > > can be seen as code move/reshuffle/cleanup and does not bring any > > functionality. I think patches 16-19 also belong to prerequisite and > > fixes and are easy to parse. > > So if we could at least have patches 1-19 merged in 10.1, this would > > alleviate the rebase efforts for next respins if any. > > > > Of course I have not totally lost all hopes to get this in in 10.1 ;-) > > and I will be able to diligently respin upon comments.
> If no one objects, I can queue this. OK with ARM maintainers? Judging by the diffstat this doesn't really touch the arm stuff specifically, so if reviewers who are familiar with hotplug and ACPI are happy that this is the correct way to do PCI hotplug for Arm and have reviewed it then I'm fine with going via the ACPI tree for whatever subset of patches you think are ready to go in. thanks -- PMM
