From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Jiang Liu <liuj97@gmail.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Len Brown <lenb@kernel.org>, Jiang Liu <jiang.liu@huawei.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Ashok Raj <ashok.raj@intel.com>,
Keping Chen <chenkeping@huawei.com>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 00/11] Enhancements and bugfixes to PCI hotplug subsystem
Date: Tue, 27 Mar 2012 12:33:01 +0900 [thread overview]
Message-ID: <4F7134ED.4040602@jp.fujitsu.com> (raw)
In-Reply-To: <1332514707-9673-1-git-send-email-jiang.liu@huawei.com>
> The second prososal is to introduce a recursive mutex lock to
> serialize all hotplug operations triggered by sysfs interfaces,
> PCI HPC hardware events, ACPI hotplug events and other sources.
The pciehp (and other hotplug controllers) needs this too.
There is only one mutex in the current implementation. I think it
would be better if we can have the mutex per host bridge or per bus
or something so that we can run multiple hot-plug operation in
parallel on the independent PCI sub trees.
Regards,
Kenji Kaneshige
(2012/03/23 23:58), Jiang Liu wrote:
> This is a series of RFC patches, to make sure we are doing the
> right thing in the right way. The patchset hasn't been tested yet.
> There are several minor bugfixes and two proposals.
>
> The first proposal is to add notification chain for PCI hotplug events,
> so other components interested in PCI root/bus/device hotplug events
> could subscribe to the chain.
>
> The second prososal is to introduce a recursive mutex lock to
> serialize all hotplug operations triggered by sysfs interfaces,
> PCI HPC hardware events, ACPI hotplug events and other sources.
>
> There are still works left in driver/pci/hotplug directory to apply
> the above two proposals.
>
> The patchset applies to Yinghai's work on PCI root bus hotplug at
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-x86-irq
> And it depends on my previous patchset, please refer to
> http://www.spinics.net/lists/linux-pci/msg14472.html
>
> Thanks!
>
> Jiang Liu (11):
> PCI: Fix device reference count leakage in pci_dev_present()
> PCI: introduce pci_bus_get()/pci_bus_put() to hide implementation
> details
> PCI: clean up root bridge related logic in acpiphp driver
> ACPI,PCI: fix race windows caused by alloc_acpi_hotplug_work()
> PCI: Add notification interfaces for PCI root/bus/device hotplug
> events
> ACPI,PCI: update ACPI<->PCI binding information when pci hotplug
> event happens
> ACPI,PCI: update ACPI slots when PCI hotplug event happens
> PCI: Introduce recursive mutex to serialize PCI hotplug operations
> PCI: serialize hotplug operations triggered by PCI hotplug sysfs
> interfaces
> PCI,ACPI: serialize hotplug operations triggered by ACPI subsystem
> PCI: Serialize hotplug operations triggered by acpiphp driver
>
> drivers/acpi/pci_bind.c | 115 +++++++++++++++++++++++++
> drivers/acpi/pci_root.c | 8 ++
> drivers/acpi/pci_slot.c | 81 ++++++++++++++++++-
> drivers/pci/bus.c | 20 ++++-
> drivers/pci/hotplug.c | 47 +++++++++++
> drivers/pci/hotplug/acpiphp.h | 7 ++-
> drivers/pci/hotplug/acpiphp_glue.c | 143 ++++++++++++--------------------
> drivers/pci/hotplug/pci_hotplug_core.c | 2 +
> drivers/pci/pci-sysfs.c | 29 +++----
> drivers/pci/pci.h | 8 ++
> drivers/pci/probe.c | 10 ++-
> drivers/pci/remove.c | 20 ++++-
> drivers/pci/search.c | 10 +-
> include/linux/pci.h | 57 +++++++++++++
> 14 files changed, 437 insertions(+), 120 deletions(-)
>
next prev parent reply other threads:[~2012-03-27 3:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 14:58 [PATCH 00/11] Enhancements and bugfixes to PCI hotplug subsystem Jiang Liu
2012-03-23 14:58 ` [PATCH 01/11] PCI: Fix device reference count leakage in pci_dev_present() Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 02/11] PCI: introduce pci_bus_get()/pci_bus_put() to hide implementation details Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 03/11] PCI: clean up root bridge related logic in acpiphp driver Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 04/11] ACPI,PCI: fix race windows caused by alloc_acpi_hotplug_work() Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 05/11] PCI: Add notification interfaces for PCI root/bus/device hotplug events Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 06/11] ACPI,PCI: update ACPI<->PCI binding information when pci hotplug event happens Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 07/11] ACPI,PCI: update ACPI slots when PCI " Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 08/11] PCI: Introduce recursive mutex to serialize PCI hotplug operations Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 09/11] PCI: serialize hotplug operations triggered by PCI hotplug sysfs interfaces Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 10/11] PCI,ACPI: serialize hotplug operations triggered by ACPI subsystem Jiang Liu
2012-03-23 14:58 ` [RFC PATCH 11/11] PCI: Serialize hotplug operations triggered by acpiphp driver Jiang Liu
2012-03-27 3:33 ` Kenji Kaneshige [this message]
2012-03-27 14:31 ` [PATCH 00/11] Enhancements and bugfixes to PCI hotplug subsystem Jiang Liu
2012-03-30 4:15 ` Kenji Kaneshige
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=4F7134ED.4040602@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=chenkeping@huawei.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jiang.liu@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--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