From: Jiang Liu <liuj97@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org
Subject: Re: [PATCH 00/10] PCI, ACPI: Use bus type notifier for root bus hotplug
Date: Sun, 07 Oct 2012 23:17:52 +0800 [thread overview]
Message-ID: <50719D20.8020009@gmail.com> (raw)
In-Reply-To: <CAE9FiQWj655cwN_e0ZmzCVYmJEnM2O_V453g4QTQqaApOPo2Fw@mail.gmail.com>
On 10/06/2012 03:25 PM, Yinghai Lu wrote:
> On Fri, Oct 5, 2012 at 7:57 PM, Jiang Liu <liuj97@gmail.com> wrote:
>> Hi Yinghai,
>> I like your idea to get rid of acpi_device_ops->start() method, actually
>> that's on my TODO list too.
>> I think the ACPI based system device hotplug framework we are working on
>> may help to solve this issue. We define CPU, memory, PCI host bridge, IOAPIC,
>> and CONTAINER as system devices. We have added some callbacks into acpi_device_ops
>> to support system device hotplug. With the new ACPI system device hotplug framework,
>> the sequence is:
>> 1) Walk hot-added ACPI subtree, creates acpi devices and binds acpi drivers. Now
>> acpi_device_ops->add() method only setup basic data structure to manage the ACPI
>> device but without actually starting the system device.
>> 2) Classify hot-added ACPI devices into classes, such CPU, MEM, PCI HOST BRIGE, IOAPIC,
>> CONTAINER.
>> 3) Add all hot-added system device into running system in following order:
>> CONTAINER -> MEM -> CPU -> IOAPIC -> PCI_HOST_BRIDGE.
>>
>> 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
>
> for-pci-x86-pcibios-alloc-res
> for-pci-host-bridge-bus-type
> for-pci-kill-pci-root-buses
>
> for-pci-root-bus-hotplug
>
> for-pci-misc
>
> for-pci-jiang-hotplug
>
> for-pci-root-bus-hotadd-survey-pcibios-res
> for-pci-split-pci-root-hp
> for-pci-notifier
>
>
> for-acpi-next-pci
> for-pci-next
>
> 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".
Thanks!
next prev parent reply other threads:[~2012-10-07 15:18 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 6:32 [PATCH 00/10] PCI, ACPI: Use bus type notifier for root bus hotplug Yinghai Lu
2012-10-02 6:32 ` [PATCH 01/10] device: add drivers_autoprobe in struct device Yinghai Lu
2012-10-02 13:33 ` Greg Kroah-Hartman
2012-10-02 17:39 ` Yinghai Lu
2012-10-02 17:47 ` Greg Kroah-Hartman
2012-10-02 18:00 ` Bjorn Helgaas
2012-10-02 20:20 ` Yinghai Lu
2012-10-02 20:45 ` Greg Kroah-Hartman
2012-10-02 21:47 ` Yinghai Lu
2012-10-02 22:38 ` Bjorn Helgaas
2012-10-02 23:20 ` Yinghai Lu
2012-10-03 0:00 ` Yinghai Lu
2012-10-03 2:07 ` Yinghai Lu
2012-10-03 2:08 ` Yinghai Lu
2012-10-03 19:48 ` Bjorn Helgaas
2012-10-03 20:50 ` Yinghai Lu
2012-10-03 23:00 ` [PATCH 0/4] ACPI: kill acpi_pci_root_start Yinghai Lu
2012-10-03 23:00 ` [PATCH 1/4] ACPI: add drivers_autoprobe in struct acpi_device Yinghai Lu
2012-10-04 13:03 ` Konrad Rzeszutek Wilk
2012-10-04 15:15 ` Yinghai Lu
2012-10-09 16:38 ` Konrad Rzeszutek Wilk
2012-10-03 23:00 ` [PATCH 2/4] ACPI: use device drivers_autoprobe to delay loading acpi drivers Yinghai Lu
2012-10-03 23:00 ` [PATCH 3/4] PCI, ACPI: Remove not used acpi_pci_root_start() Yinghai Lu
2012-10-03 23:00 ` [PATCH 4/4] ACPI: remove acpi_op_start workaround Yinghai Lu
2012-10-04 12:57 ` Konrad Rzeszutek Wilk
2012-10-04 17:47 ` [PATCH 0/4] ACPI: kill acpi_pci_root_start Bjorn Helgaas
2012-10-04 18:36 ` Yinghai Lu
2012-10-04 19:44 ` Bjorn Helgaas
2012-10-04 19:54 ` Rafael J. Wysocki
2012-10-04 20:14 ` Yinghai Lu
2012-10-04 20:47 ` Bjorn Helgaas
2012-10-04 19:53 ` Rafael J. Wysocki
2012-10-04 21:23 ` Rafael J. Wysocki
2012-10-04 21:31 ` Yinghai Lu
2012-10-04 21:53 ` Rafael J. Wysocki
2012-10-04 22:01 ` Yinghai Lu
2012-10-04 22:36 ` Rafael J. Wysocki
2012-10-04 22:46 ` Yinghai Lu
2012-10-05 23:01 ` Rafael J. Wysocki
2012-10-05 23:10 ` Yinghai Lu
2012-10-08 20:12 ` Rafael J. Wysocki
2012-10-02 6:33 ` [PATCH 02/10] ACPI: use device drivers_autoprobe to delay loading acpi drivers Yinghai Lu
2012-10-02 6:33 ` [PATCH 03/10] PCI: prepare to use device drivers_autoprobe to delay attach drivers Yinghai Lu
2012-10-02 6:33 ` [PATCH 04/10] PCI: Use device_add for device and bus early Yinghai Lu
2012-10-02 6:33 ` [PATCH 05/10] PCI, ACPI: Separate out acpi_pci_root_osc_contorl_set Yinghai Lu
2012-10-02 6:33 ` [PATCH 06/10] PCI, ACPI: Move hot add root bus conf code to acpi_pci_root_add Yinghai Lu
2012-10-02 6:33 ` [PATCH 07/10] PCI, ACPI: Remove not used acpi_pci_root_start() Yinghai Lu
2012-10-02 6:33 ` [PATCH 08/10] PCI: Add dev_is_pci_host_bridge() helper Yinghai Lu
2012-10-02 6:33 ` [PATCH 09/10] PCI, ACPI: using acpi/pci bind path for pci_host_bridge Yinghai Lu
2012-10-02 6:33 ` [PATCH 10/10] PCI, ACPI: use bus_type notifier for acpi_pci_bind_notify Yinghai Lu
2012-10-06 2:57 ` [PATCH 00/10] PCI, ACPI: Use bus type notifier for root bus hotplug Jiang Liu
2012-10-06 7:25 ` Yinghai Lu
2012-10-07 15:17 ` Jiang Liu [this message]
2012-10-07 22:33 ` Yinghai Lu
2012-10-08 15:23 ` Jiang Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50719D20.8020009@gmail.com \
--to=liuj97@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).