From: wangyijing <wangyijing@huawei.com>
To: bhelgaas@google.com
Cc: rjw@rjwysocki.net, linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: release pci_host_bridge resource after remove root bus
Date: Mon, 25 Jul 2016 09:18:27 +0800 [thread overview]
Message-ID: <579568E3.6010601@huawei.com> (raw)
In-Reply-To: <1466682138-25281-1-git-send-email-wangyijing@huawei.com>
ping..
在 2016/6/23 19:42, Yijing Wang 写道:
> pci_host_bridge holds the top resources(IO port/Mem/bus),
> now we release pci_host_bridge resources in
> acpi_pci_root_release_info() which would be called when
> pci_host_bridge device refcount reach 0. In some cases,
> pci_host_bridge refcount cannot reach 0 after we remove
> pci root bus in pci_remove_root_bus(). Then if we want to
> hot add pci root bus, we cannot use pci_host_bridge
> resources because of conflicts with old resources which are
> still in system. I think this is not reasonable.
>
> 1. For pci devices, we would release their resources in
> pci_destroy_dev() regardless of pci device refcount.
> 2. When we try to remove pci root bus, there is no devices
> need to use the pci_host_bridge resources again, release
> pci_host_bridge resources is safe.
> 3. In some cases, users woule make mistake, for example,
> user get a pci device(increase refcount), but forget to
> put this device, then if we do hotplug pci root bus,
> it would make all pci devices cannot work after hot add.
>
> I found this issue in the following case:
> 1. I have a raid pci device in my system;
> 2. I mount a disk which connect to this raid.
> 3. hot remove the pci root bus.
> 4. hot add the pci root bus.
> 5. found the resource conflicts for the children pci devices under this root bus.
>
> pci_root_bus increase a refcount at pci_host_bridge.
> pci_root_bus decrease a refcount at pci_host_bridge in
> release_pcibus_dev() when pci_root_bus device refcount reach 0.
>
> pci_dev increase a refcount at pci_bus in pci_alloc_dev().
> pci_dev decrease a refcount at pci_bus in pci_release_dev()
> when pci_dev refcount reach 0.
>
> If any pci device refcount cannot reach 0, then its pci_bus
> refcount cannot reach 0 too, the result is pci_host_bridge
> refcount cannot reach 0.
>
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> ---
> drivers/acpi/pci_root.c | 11 -----------
> drivers/pci/host-bridge.c | 15 +++++++++++++++
> drivers/pci/pci.h | 2 +-
> drivers/pci/remove.c | 1 +
> 4 files changed, 17 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/acpi/pci_root.c b/drivers/acpi/pci_root.c
> index d144168..c5142d0 100644
> --- a/drivers/acpi/pci_root.c
> +++ b/drivers/acpi/pci_root.c
> @@ -839,17 +839,6 @@ static void __acpi_pci_root_release_info(struct acpi_pci_root_info *info)
>
> static void acpi_pci_root_release_info(struct pci_host_bridge *bridge)
> {
> - struct resource *res;
> - struct resource_entry *entry;
> -
> - resource_list_for_each_entry(entry, &bridge->windows) {
> - res = entry->res;
> - if (res->flags & IORESOURCE_IO)
> - pci_unmap_iospace(res);
> - if (res->parent &&
> - (res->flags & (IORESOURCE_MEM | IORESOURCE_IO)))
> - release_resource(res);
> - }
> __acpi_pci_root_release_info(bridge->release_data);
> }
>
> diff --git a/drivers/pci/host-bridge.c b/drivers/pci/host-bridge.c
> index 5f4a2e0..3594967 100644
> --- a/drivers/pci/host-bridge.c
> +++ b/drivers/pci/host-bridge.c
> @@ -8,6 +8,21 @@
>
> #include "pci.h"
>
> +void release_host_bridge_resources(struct pci_host_bridge *bridge)
> +{
> + struct resource *res;
> + struct resource_entry *entry;
> +
> + resource_list_for_each_entry(entry, &bridge->windows) {
> + res = entry->res;
> + if (res->flags & IORESOURCE_IO)
> + pci_unmap_iospace(res);
> + if (res->parent &&
> + (res->flags & (IORESOURCE_MEM | IORESOURCE_IO)))
> + release_resource(res);
> + }
> +}
> +
> static struct pci_bus *find_pci_root_bus(struct pci_bus *bus)
> {
> while (bus->parent)
> diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
> index 9730c47..46725d9 100644
> --- a/drivers/pci/pci.h
> +++ b/drivers/pci/pci.h
> @@ -11,7 +11,7 @@ extern const unsigned char pcie_link_speed[];
> bool pcie_cap_has_lnkctl(const struct pci_dev *dev);
>
> /* Functions internal to the PCI core code */
> -
> +void release_host_bridge_resources(struct pci_host_bridge *bridge);
> int pci_create_sysfs_dev_files(struct pci_dev *pdev);
> void pci_remove_sysfs_dev_files(struct pci_dev *pdev);
> #if !defined(CONFIG_DMI) && !defined(CONFIG_ACPI)
> diff --git a/drivers/pci/remove.c b/drivers/pci/remove.c
> index d1ef7ac..a42b396 100644
> --- a/drivers/pci/remove.c
> +++ b/drivers/pci/remove.c
> @@ -161,6 +161,7 @@ void pci_remove_root_bus(struct pci_bus *bus)
> pci_remove_bus(bus);
> host_bridge->bus = NULL;
>
> + release_host_bridge_resources(host_bridge);
> /* remove the host bridge */
> device_unregister(&host_bridge->dev);
> }
>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-07-25 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 11:42 [PATCH] PCI: release pci_host_bridge resource after remove root bus Yijing Wang
2016-07-25 1:18 ` wangyijing [this message]
2016-08-22 17:28 ` Bjorn Helgaas
2016-08-23 2:22 ` wangyijing
2016-08-24 21:39 ` Bjorn Helgaas
2016-08-24 21:48 ` Sinan Kaya
2016-08-25 8:16 ` wangyijing
2016-08-25 8:01 ` wangyijing
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=579568E3.6010601@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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