From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: Liviu Dudau <liviu@dudau.co.uk>, Tony Luck <tony.luck@intel.com>,
Russell King <linux@arm.linux.org.uk>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"huxinwei@huawei.com" <huxinwei@huawei.com>,
Thierry Reding <thierry.reding@gmail.com>,
Yijing Wang <wangyijing0307@gmail.com>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Wuyun <wuyun.wu@huawei.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH 08/16] PCI: Introduce pci_scan_host_bridge() and pci_host_info
Date: Tue, 18 Nov 2014 15:42:43 +0000 [thread overview]
Message-ID: <20141118154243.GM12037@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <1416219710-26088-9-git-send-email-wangyijing@huawei.com>
On Mon, Nov 17, 2014 at 10:21:42AM +0000, Yijing Wang wrote:
> From: Yijing Wang <wangyijing0307@gmail.com>
>=20
> Now pci_host_bridge has been ripped out from pci root
> bus creation. Currently pci_scan_root_bus() lacks
> scalability, so platform host drivers have no proper
> way to configure pci_host_bridge. E.g we should assign
> msi_controller to pci_host_bridge, add argument for
> pci_scan_root_bus() is not a good idea, it has already
> five, so introudce struct pci_host_info to make
> pci scan interfaces more scalable. Because almost
> all host drivers need to configure host resources,
> so we put .init_res() in it first, and add other
> hooks when need.
>=20
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> ---
> drivers/pci/host-bridge.c | 27 +++++++++-------
> drivers/pci/probe.c | 73 +++++++++++++++++++++++++++++++++++++++=
+++--
> include/linux/pci.h | 20 ++++++++++++-
> 3 files changed, 103 insertions(+), 17 deletions(-)
>=20
> diff --git a/drivers/pci/host-bridge.c b/drivers/pci/host-bridge.c
> index e31604f..49b6c21 100644
> --- a/drivers/pci/host-bridge.c
> +++ b/drivers/pci/host-bridge.c
> @@ -8,9 +8,6 @@
> =20
> #include "pci.h"
> =20
> -LIST_HEAD(pci_host_bridge_list);
> -DECLARE_RWSEM(pci_host_bridge_sem);
> -
> static struct resource busn_resource =3D {
> =09.name=09=3D "PCI busn",
> =09.start=09=3D 0,
> @@ -18,6 +15,9 @@ static struct resource busn_resource =3D {
> =09.flags=09=3D IORESOURCE_BUS,
> };
> =20
> +LIST_HEAD(pci_host_bridge_list);
> +DECLARE_RWSEM(pci_host_bridge_sem);
> +
> static void pci_release_host_bridge_dev(struct device *dev)
> {
> =09struct pci_host_bridge *bridge =3D to_pci_host_bridge(dev);
> @@ -29,14 +29,12 @@ static void pci_release_host_bridge_dev(struct device=
*dev)
> }
> =20
> struct pci_host_bridge *pci_create_host_bridge(
> -=09=09struct device *parent, u32 db,=20
> -=09=09struct pci_ops *ops, void *sysdata,=20
> -=09=09struct list_head *resources)
> +=09=09struct device *parent, u32 db, struct pci_ops *ops,=20
> +=09=09struct pci_host_info *info)
> {
> =09int error;
> =09struct pci_bus *b;
> =09struct pci_host_bridge *host, *h;
> -=09struct pci_host_bridge_window *window, *n;
> =20
> =09down_read(&pci_host_bridge_sem);
> =09list_for_each_entry(h, &pci_host_bridge_list, list) {
> @@ -53,7 +51,7 @@ struct pci_host_bridge *pci_create_host_bridge(
> =09if (!host)
> =09=09return NULL;
> =20
> -=09host->sysdata =3D sysdata;
> +=09host->sysdata =3D info->arg;
> =09host->busnum =3D PCI_BUSNUM(db);
> =09host->domain =3D PCI_DOMAIN(db);
> =09host->ops =3D ops;
> @@ -63,18 +61,23 @@ struct pci_host_bridge *pci_create_host_bridge(
> =20
> =09/* this is hack, just for build, will be removed later*/
Why do you need this hack? Just for calling pci_domain_nr() ?
> =09b =3D kzalloc(sizeof(*b), GFP_KERNEL);
> -=09b->sysdata =3D sysdata;
> +=09b->sysdata =3D host->sysdata;
> =09pci_bus_assign_domain_nr(b, parent);
> =09host->domain =3D pci_domain_nr(b);
> +=09kfree(b);
> =20
> -=09if (!resources) {
> +=09if (info->res_type =3D=3D PCI_HOST_RES_DEFAULT) {
> =09=09/* Use default IO/MEM/BUS resources*/
> =09=09pci_add_resource(&host->windows, &ioport_resource);
> =09=09pci_add_resource(&host->windows, &iomem_resource);
> =09=09pci_add_resource(&host->windows, &busn_resource);
> =09} else {
> -=09=09list_for_each_entry_safe(window, n, resources, list)
> -=09=09=09list_move_tail(&window->list, &host->windows);
> +=09=09if (!info->init_res || info->init_res(host, info)) {
> +=09=09=09pr_err("pci host %04x:%02x init resources fail\n",
> +=09=09=09=09=09host->domain, host->busnum);
> +=09=09=09kfree(host);
> +=09=09=09return NULL;
> +=09=09}
> =09}
> =20
> =09dev_set_name(&host->dev, "pci%04x:%02x", host->domain,=20
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index d472da4..42158fd 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -1863,6 +1863,21 @@ void __weak pcibios_remove_bus(struct pci_bus *bus=
)
> {
> }
> =20
> +static int pci_default_init_res(struct pci_host_bridge *host,
> +=09=09struct pci_host_info *info)
> +{
> +=09struct pci_host_bridge_window *window, *n;
> +
> +=09if (info->res_type !=3D PCI_HOST_RES_DEFAULT)=20
> +=09=09list_for_each_entry_safe(window, n, info->resources,
> +=09=09=09=09list)
> +=09=09=09list_move_tail(&window->list, &host->windows);
> +=09else
> +=09=09info->res_type =3D PCI_HOST_RES_DEFAULT;
I'm confused about this assignment. Isn't this a nop as the else part
means info->res_type *is* PCI_HOST_RES_DEFAULT?
> +
> +=09return 0;
> +}
> +
> struct pci_bus *__pci_create_root_bus(struct pci_host_bridge *bridge)
> {
> =09int error;
> @@ -1949,13 +1964,17 @@ err_out:
> =09return NULL;
> }
> =20
> -struct pci_bus *pci_create_root_bus(struct device *parent, u32 bus,
> +struct pci_bus *pci_create_root_bus(struct device *parent, u32 db,
> =09=09struct pci_ops *ops, void *sysdata, struct list_head *resources)
> {
> =09struct pci_host_bridge *host;
> +=09struct pci_host_info info;
> +=09
> +=09info.arg=3D sysdata;
> +=09info.resources =3D resources;
> +=09info.init_res =3D pci_default_init_res;
> =20
> -=09host =3D pci_create_host_bridge(parent, bus, ops,=20
> -=09=09=09sysdata ,resources);
> +=09host =3D pci_create_host_bridge(parent, db, ops, &info);
> =09if (!host)
> =09=09return NULL;
> =20
> @@ -2038,8 +2057,13 @@ struct pci_bus *pci_scan_root_bus(struct device *p=
arent, u32 db,
> =09bool found =3D false;
> =09struct pci_host_bridge *host;
> =09int max;
> +=09struct pci_host_info info;
> +=09
> +=09info.arg =3D sysdata;
> +=09info.resources =3D resources;
> +=09info.init_res =3D pci_default_init_res;
I have mixed feelings about this patch. While it is heading in the right di=
rection
of moving pci_host_bridge relevant information towards the right user, I do=
n't think
you picked up the right set to move. The resource list is going to be copie=
d into
internal pci_host_bridge list anyway, keeping another copy is not helpful *=
and*
you have increased the code size.
I think for now we should aim to get the *missing* data into pci_host_bridg=
e: MSI
controllers and PCI domain/segment. Then we can do more cleanup.
> =20
> -=09host =3D pci_create_host_bridge(parent, db, ops, sysdata, resources);
> +=09host =3D pci_create_host_bridge(parent, db, ops, &info);
> =09if (!host)
> =09=09return NULL;
> =20
> @@ -2070,6 +2094,47 @@ struct pci_bus *pci_scan_root_bus(struct device *p=
arent, u32 db,
> }
> EXPORT_SYMBOL(pci_scan_root_bus);
> =20
> +struct pci_host_bridge *pci_scan_host_bridge(
> +=09=09struct device *parent, u32 db, struct pci_ops *ops,
> +=09=09struct pci_host_info *info)
> +{
> +=09struct pci_host_bridge_window *window;
> +=09bool found =3D false;
> +=09struct pci_host_bridge *host;
> +=09int max;
> +
> +=09host =3D pci_create_host_bridge(parent, db, ops, info);
> +=09if (!host)
> +=09=09return NULL;
> +
> +=09list_for_each_entry(window, &host->windows, list)
> +=09=09if (window->res->flags & IORESOURCE_BUS) {
> +=09=09=09found =3D true;
> +=09=09=09break;
> +=09=09}
> +
> +=09host->bus =3D __pci_create_root_bus(host);
> +=09if (!host->bus) {
> +=09=09pci_free_host_bridge(host);
> +=09=09return NULL;
> +=09}
> +
> +=09if (!found) {
> +=09=09dev_info(&host->bus->dev,
> +=09=09 "No busn resource found for root bus, will use [bus %02x-ff]\n",
> +=09=09=09host->busnum);
> +=09=09pci_bus_insert_busn_res(host->bus, host->busnum, 255);
> +=09}
> +
> +=09max =3D pci_scan_child_bus(host->bus);
> +=09if (!found)
> +=09=09pci_bus_update_busn_res_end(host->bus, max);
> +
> +=09return host;
> +
> +}
> +EXPORT_SYMBOL(pci_scan_host_bridge);
> +
> /**
> * pci_rescan_bus_bridge_resize - scan a PCI bus for devices.
> * @bridge: PCI bridge for the bus to scan
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index daa7f40..a51f5f5 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -412,6 +412,21 @@ struct pci_host_bridge {
> =09void *release_data;
> };
> =20
> +struct pci_host_info {
> +=09u8 res_type;
> +=09void *arg;
> +=09struct list_head *resources; /*just for build, will clean up later */
> +=09int (*init_res)(struct pci_host_bridge *host,=20
> +=09=09=09struct pci_host_info *info);
> +};
> +
> +static inline void init_pci_host_info(struct pci_host_info *info)
> +{
> +=09memset(info, 0 , sizeof(*info));
> +}
Where is this used?
> +
> +#define PCI_HOST_RES_DEFAULT=090x2
> +
Magic number?
Best regards,
Liviu
> #define=09to_pci_host_bridge(n) container_of(n, struct pci_host_bridge, =
dev)
> void pci_set_host_bridge_release(struct pci_host_bridge *bridge,
> =09=09 void (*release_fn)(struct pci_host_bridge *),
> @@ -420,7 +435,7 @@ void pci_set_host_bridge_release(struct pci_host_brid=
ge *bridge,
> int pcibios_root_bridge_prepare(struct pci_host_bridge *bridge);
> struct pci_host_bridge *pci_create_host_bridge(
> =09=09struct device *parent, u32 db, struct pci_ops *ops,=20
> -=09=09void *sys, struct list_head *resources);
> +=09=09struct pci_host_info *info);
> /*
> * The first PCI_BRIDGE_RESOURCE_NUM PCI bus resources (those that corre=
spond
> * to P2P or CardBus bridge windows) go in a table. Additional ones (fo=
r
> @@ -785,6 +800,9 @@ void pci_bus_release_busn_res(struct pci_bus *b);
> struct pci_bus *pci_scan_root_bus(struct device *parent, u32 bus,
> =09=09=09=09=09 struct pci_ops *ops, void *sysdata,
> =09=09=09=09=09 struct list_head *resources);
> +struct pci_host_bridge *pci_scan_host_bridge(struct device *parent,
> +=09=09u32 db, struct pci_ops *ops,
> +=09=09struct pci_host_info *info);
> struct pci_bus *pci_add_new_bus(struct pci_bus *parent, struct pci_dev *=
dev,
> =09=09=09=09int busnr);
> void pcie_update_link_speed(struct pci_bus *bus, u16 link_status);
> --=20
> 1.7.1
>=20
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>=20
--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
=C2=AF\_(=E3=83=84)_/=C2=AF
next prev parent reply other threads:[~2014-11-18 15:42 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 10:21 [RFC PATCH 00/16] Refine PCI host bridge scan interfaces Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 01/16] PCI: Enhance pci_scan_root_bus() to support default IO/MEM resources Yijing Wang
2014-11-17 10:08 ` Arnd Bergmann
2014-11-18 7:44 ` Yijing Wang
2014-11-18 9:36 ` Arnd Bergmann
2014-11-18 11:46 ` Yijing Wang
2014-11-18 14:23 ` Liviu Dudau
2014-11-19 1:15 ` Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 02/16] PCI: Use pci_scan_root_bus() instead of pci_scan_bus() Yijing Wang
2014-11-18 14:28 ` Liviu Dudau
2014-11-19 1:19 ` Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 03/16] PCI: Clean up pci_scan_bus() Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 04/16] PCI: Rip out pci_bus_add_devices() from pci_scan_root_bus() Yijing Wang
2014-11-18 14:34 ` Liviu Dudau
2014-11-19 1:21 ` Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 05/16] PCI: Use pci_scan_root_bus() instead of pci_scan_bus_parented() Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 06/16] PCI: Use u32 type to combine PCI domain and bus number Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 07/16] PCI: Separate pci_host_bridge creation out of pci_create_root_bus() Yijing Wang
2014-11-17 10:56 ` Arnd Bergmann
2014-11-18 8:32 ` Yijing Wang
2014-11-18 9:30 ` Arnd Bergmann
2014-11-18 11:44 ` Yijing Wang
2014-11-18 12:25 ` Arnd Bergmann
2014-11-18 12:41 ` Yijing Wang
2014-11-18 14:48 ` Liviu Dudau
2014-11-19 2:24 ` Yijing Wang
2014-11-19 16:29 ` Liviu Dudau
2014-11-20 2:00 ` Yijing Wang
2014-11-18 15:30 ` Liviu Dudau
2014-11-19 1:42 ` Yijing Wang
2014-11-19 16:37 ` Liviu Dudau
2014-11-20 2:47 ` Yijing Wang
2014-11-20 9:47 ` Liviu Dudau
2014-11-21 2:53 ` Yijing Wang
2014-11-21 9:53 ` Liviu Dudau
2014-11-17 10:21 ` [RFC PATCH 08/16] PCI: Introduce pci_scan_host_bridge() and pci_host_info Yijing Wang
2014-11-18 15:42 ` Liviu Dudau [this message]
2014-11-19 2:09 ` Yijing Wang
2014-11-19 16:41 ` Liviu Dudau
2014-11-20 2:54 ` Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 09/16] PCI: Associate .get_msi_ctrl() with pci_host_bridge Yijing Wang
2014-11-17 15:03 ` Lorenzo Pieralisi
2014-11-17 10:21 ` [RFC PATCH 10/16] PCI: Add of_scan_bus() to pci_host_info Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 11/16] x86/PCI: Use pci_scan_host_bridge() instead of pci_create_root_bus() Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 12/16] ia64/PCI: Remove the redundant bus variable Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 13/16] ia64/PCI: Use pci_scan_host_bridge() to refactor pci_acpi_scan_root() Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 14/16] arm/PCI: Introduce pci_get_domain_nr() Yijing Wang
2014-11-17 12:08 ` Lorenzo Pieralisi
2014-11-18 0:55 ` Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 15/16] arm/PCI: Use pci_scan_host_bridge() instead of pci_scan_root_bus() Yijing Wang
2014-11-17 10:21 ` [RFC PATCH 16/16] powerpc/PCI: Use pci_scan_host_bridge() to scan PCI bus Yijing Wang
2014-11-17 14:13 ` [RFC PATCH 00/16] Refine PCI host bridge scan interfaces Arnd Bergmann
2014-11-18 11:17 ` Yijing Wang
2014-11-18 11:30 ` Arnd Bergmann
2014-11-18 11:45 ` Lorenzo Pieralisi
2014-11-18 12:14 ` Yijing Wang
2014-11-18 12:17 ` Yijing Wang
2014-11-18 12:27 ` Arnd Bergmann
2014-11-20 12:01 ` Tomasz Nowicki
2014-11-20 13:15 ` Arnd Bergmann
2014-11-20 11:54 ` Tomasz Nowicki
2014-11-20 12:08 ` Liviu Dudau
2014-11-20 12:53 ` Tomasz Nowicki
2014-11-20 16:39 ` Liviu Dudau
2014-11-21 2:58 ` Yijing Wang
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=20141118154243.GM12037@e106497-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=bhelgaas@google.com \
--cc=huxinwei@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liviu@dudau.co.uk \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=tony.luck@intel.com \
--cc=wangyijing0307@gmail.com \
--cc=wangyijing@huawei.com \
--cc=wuyun.wu@huawei.com \
--cc=x86@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).