On Sun, Oct 7, 2012 at 8:17 AM, Jiang Liu <liuj97@xxxxxxxxx> wrote: > On 10/06/2012 03:25 PM, Yinghai Lu wrote: >>> With above sequence, we could scan and start PCI devices in step 3 above. >> >> ioapic may need to be after pci device scan and pci assign-unassigned resource. >> >> the same as iommu/dmar... need to after pci device scanning... > Hi Yinghai, > I have no experience with AMD IOAPIC yet, seems IOAPIC on AMD platforms > may have the special requirement above. So your solution is better and no need > for the ACPI system device hotplug framework to handle IOAPIC device any more. > >> >> I have all pci root bus hot plug related patch in my tree >> ... >> >> after those patches (about 61) go through pci/next >> >> will need to push for-x86-irq for ioapic through tip >> and for-iommu for iommu support through iommu : david.W > I have reviewed these branches, all seems great to me. It includes some nice clean > up other than the "PCI host bridge hotplug". > for-pci-split-pci-root-hp > for-pci-root-bus-hotplug > for-pci-misc > for-pci-host-bridge-bus-type > for-pci-jiang-hotplug > for-pci-notifier > for-pci-x86-pcibios-alloc-res > for-pci-root-bus-hotadd-survey-pcibios-res > > And we I have several plan based on your work as below, what's your thoughts? > 1) replace pci_root_hp.c with our new hotplug framework > 2) enhance pci_root.c to support new hotplug framework > 3) enable PCI host bridge hotplug for IA64 platforms. > 4) try to make PCI host bridge hotplug work without "drivers_autoprobe". I think my pci-root-bus hotplug should be all done. need to flush all patches except last 7 patches about drivers_autoprobe. my concern about your new acpihp framework: please make sure you change will still make user have the chance not to use acpiphp for normal pci slot hotplug support instead of pciehp. Also I would suggest you to start the new framework stuff after cpu, memory, pci-root-bus work are all done separately. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
