From: Bjorn Helgaas <bhelgaas@google.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: linux-pci@vger.kernel.org, Wei Yang <weiyang@linux.vnet.ibm.com>,
benh@au1.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V11 08/17] powrepc/pci: Refactor pci_dn
Date: Tue, 24 Feb 2015 02:13:30 -0600 [thread overview]
Message-ID: <20150224081330.GE6220@google.com> (raw)
In-Reply-To: <20150223001349.GA7522@shangw>
On Mon, Feb 23, 2015 at 11:13:49AM +1100, Gavin Shan wrote:
> On Fri, Feb 20, 2015 at 05:19:17PM -0600, Bjorn Helgaas wrote:
> >On Thu, Jan 15, 2015 at 10:27:58AM +0800, Wei Yang wrote:
> >> From: Gavin Shan <gwshan@linux.vnet.ibm.com>
> >>
> >> pci_dn is the extension of PCI device node and it's created from
> >> device node. Unfortunately, VFs that are enabled dynamically by
> >> PF's driver and they don't have corresponding device nodes, and
> >> pci_dn. The patch refactors pci_dn to support VFs:
> >>
> >> * pci_dn is organized as a hierarchy tree. VF's pci_dn is put
> >> to the child list of pci_dn of PF's bridge. pci_dn of other
> >> device put to the child list of pci_dn of its upstream bridge.
> >>
> >> * VF's pci_dn is expected to be created dynamically when PF
> >> enabling VFs. VF's pci_dn will be destroyed when PF disabling
> >> VFs. pci_dn of other device is still created from device node
> >> as before.
> >>
> >> * For one particular PCI device (VF or not), its pci_dn can be
> >> found from pdev->dev.archdata.firmware_data, PCI_DN(devnode),
> >> or parent's list. The fast path (fetching pci_dn through PCI
> >> device instance) is populated during early fixup time.
> >>
> >> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
> >> ---
> >> arch/powerpc/include/asm/device.h | 3 +
> >> arch/powerpc/include/asm/pci-bridge.h | 14 +-
> >> arch/powerpc/kernel/pci_dn.c | 242 ++++++++++++++++++++++++++++-
> >> arch/powerpc/platforms/powernv/pci-ioda.c | 16 ++
> >> 4 files changed, 270 insertions(+), 5 deletions(-)
> >> ...
> >
> >> +#ifdef CONFIG_PCI_IOV
> >> +static struct pci_dn *add_one_dev_pci_info(struct pci_dn *parent,
> >> + struct pci_dev *pdev,
> >> + int busno, int devfn)
> >> +{
> >> + struct pci_dn *pdn;
> >> +
> >> + /* Except PHB, we always have parent firmware data */
> >> + if (!parent)
> >> + return NULL;
> >> +
> >> + pdn = kzalloc(sizeof(*pdn), GFP_KERNEL);
> >> + if (!pdn) {
> >> + pr_warn("%s: Out of memory !\n", __func__);
> >> + return NULL;
> >> + }
> >> +
> >> + pdn->phb = parent->phb;
> >> + pdn->parent = parent;
> >> + pdn->busno = busno;
> >> + pdn->devfn = devfn;
> >> +#ifdef CONFIG_PPC_POWERNV
> >> + pdn->pe_number = IODA_INVALID_PE;
> >> +#endif
> >> + INIT_LIST_HEAD(&pdn->child_list);
> >> + INIT_LIST_HEAD(&pdn->list);
> >> + list_add_tail(&pdn->list, &parent->child_list);
> >> +
> >> + /*
> >> + * If we already have PCI device instance, lets
> >> + * bind them.
> >> + */
> >> + if (pdev)
> >> + pdev->dev.archdata.firmware_data = pdn;
> >> +
> >> + return pdn;
> >
> >I'd like to see this done in pcibios_add_device(), as I mentioned in
> >response to "[PATCH V11 01/17] PCI/IOV: Export interface for retrieve VF's
> >BDF". Maybe that's not feasible for some reason, but it would be a nicer
> >design if it's possible.
> >
> >The remove_dev_pci_info() work would be done in pcibios_release_device()
> >then, of course.
> >
>
> Yes, it's not feasible. PCI config accessors rely on VF's pci_dn. Before
> calling pcibios_add_device(), we need access VF's config space. That means
> we need VF's pci_dn before pci_setup_device() as follows:
>
> sriov_enable()
> pcibios_sriov_enable(); /* Currently, VF's pci_dn is created at this point */
> virtfn_add();
> virtfn_add_bus(); /* Create virtual bus if necessary */
> /* ---> A */
> pci_alloc_dev(); /* ---> B */
> pci_setup_device(vf); /* Access VF's config space */
> pci_read_config_byte(vf, PCI_HEADER_TYPE);
> pci_read_config_dword(vf, PCI_CLASS_REVISION);
> pci_fixup_device(pci_fixup_early, vf);
> pci_read_irq();
> pci_read_bases();
> pci_device_add(vf);
> device_initialize(&vf->dev);
> pci_fixup_device(pci_fixup_header, vf);
> pci_init_capabilities(vf);
> pcibios_add_device(vf);
>
> We have couple of options here:
>
> 1) Keep current code. VF's pci_dn is going to be destroyed in
> pcibios_sriov_disable() as we're doing currently.
> 2) Introduce pcibios_iov_virtfn_add() (at A) for platform to override.
> VF's pci_dn is going to be destroyed in pcibios_release_device().
> 3) Introduce pcibios_alloc_dev() (at B) for platform to override. The
> VF's pci_dn is going to be destroyed in pcibios_release_device().
Ah, yes, now I see the problem. I don't really like having to export
pci_iov_virtfn_bus() and pci_iov_virtfn_devfn(), but it's probably not
worth the hassle of changing it, and I think adding more pcibios interfaces
would be even worse.
So let's leave it as-is for now.
> >> +}
> >> +#endif // CONFIG_PCI_IOV
> >> +
> >> +struct pci_dn *add_dev_pci_info(struct pci_dev *pdev, u16 vf_num)
> >> +{
> >> +#ifdef CONFIG_PCI_IOV
> >> + struct pci_dn *parent, *pdn;
> >> + int i;
> >> +
> >> + /* Only support IOV for now */
> >> + if (!pdev->is_physfn)
> >> + return pci_get_pdn(pdev);
> >> +
> >> + /* Check if VFs have been populated */
> >> + pdn = pci_get_pdn(pdev);
> >> + if (!pdn || (pdn->flags & PCI_DN_FLAG_IOV_VF))
> >> + return NULL;
> >> +
> >> + pdn->flags |= PCI_DN_FLAG_IOV_VF;
> >> + parent = pci_bus_to_pdn(pdev->bus);
> >> + if (!parent)
> >> return NULL;
> >> - return PCI_DN(dn);
> >> +
> >> + for (i = 0; i < vf_num; i++) {
> >> + pdn = add_one_dev_pci_info(parent, NULL,
> >> + pci_iov_virtfn_bus(pdev, i),
> >> + pci_iov_virtfn_devfn(pdev, i));
> >> + if (!pdn) {
> >> + pr_warn("%s: Cannot create firmware data "
> >> + "for VF#%d of %s\n",
> >> + __func__, i, pci_name(pdev));
> >> + return NULL;
> >> + }
> >> + }
> >> +#endif
> >> +
> >> + return pci_get_pdn(pdev);
> >> +}
> >> +
> >> +void remove_dev_pci_info(struct pci_dev *pdev, u16 vf_num)
> >> +{
> >> +#ifdef CONFIG_PCI_IOV
> >> + struct pci_dn *parent;
> >> + struct pci_dn *pdn, *tmp;
> >> + int i;
> >> +
> >> + /* Only support IOV PF for now */
> >> + if (!pdev->is_physfn)
> >> + return;
> >> +
> >> + /* Check if VFs have been populated */
> >> + pdn = pci_get_pdn(pdev);
> >> + if (!pdn || !(pdn->flags & PCI_DN_FLAG_IOV_VF))
> >> + return;
> >> +
> >> + pdn->flags &= ~PCI_DN_FLAG_IOV_VF;
> >> + parent = pci_bus_to_pdn(pdev->bus);
> >> + if (!parent)
> >> + return;
> >> +
> >> + /*
> >> + * We might introduce flag to pci_dn in future
> >> + * so that we can release VF's firmware data in
> >> + * a batch mode.
> >> + */
> >> + for (i = 0; i < vf_num; i++) {
> >> + list_for_each_entry_safe(pdn, tmp,
> >> + &parent->child_list, list) {
> >> + if (pdn->busno != pci_iov_virtfn_bus(pdev, i) ||
> >> + pdn->devfn != pci_iov_virtfn_devfn(pdev, i))
> >> + continue;
> >> +
> >> + if (!list_empty(&pdn->list))
> >> + list_del(&pdn->list);
> >> + kfree(pdn);
> >> + }
> >> + }
> >> +#endif
> >> }
> >
>
next prev parent reply other threads:[~2015-02-24 8:13 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 5:54 [PATCH V10 00/17] Enable SRIOV on Power8 Wei Yang
2014-12-22 5:54 ` [PATCH V10 01/17] PCI/IOV: Export interface for retrieve VF's BDF Wei Yang
2014-12-22 5:54 ` [PATCH V10 02/17] PCI/IOV: add VF enable/disable hook Wei Yang
2014-12-22 5:54 ` [PATCH V10 03/17] PCI: Add weak pcibios_iov_resource_alignment() interface Wei Yang
2014-12-22 5:54 ` [PATCH V10 04/17] PCI: Store VF BAR size in pci_sriov Wei Yang
2014-12-22 5:54 ` [PATCH V10 05/17] PCI: Take additional PF's IOV BAR alignment in sizing and assigning Wei Yang
2014-12-22 5:54 ` [PATCH V10 06/17] powerpc/pci: Add PCI resource alignment documentation Wei Yang
2014-12-22 5:54 ` [PATCH V10 07/17] powerpc/pci: Don't unset pci resources for VFs Wei Yang
2014-12-22 5:54 ` [PATCH V10 08/17] powrepc/pci: Refactor pci_dn Wei Yang
2014-12-22 5:54 ` [PATCH V10 09/17] powerpc/pci: remove pci_dn->pcidev field Wei Yang
2014-12-22 5:54 ` [PATCH V10 10/17] powerpc/powernv: Use pci_dn in PCI config accessor Wei Yang
2014-12-22 5:54 ` [PATCH V10 11/17] powerpc/powernv: Allocate pe->iommu_table dynamically Wei Yang
2014-12-22 5:54 ` [PATCH V10 12/17] powerpc/powernv: Reserve additional space for IOV BAR according to the number of total_pe Wei Yang
2014-12-22 5:54 ` [PATCH V10 13/17] powerpc/powernv: Implement pcibios_iov_resource_alignment() on powernv Wei Yang
2014-12-22 5:54 ` [PATCH V10 14/17] powerpc/powernv: Shift VF resource with an offset Wei Yang
2014-12-22 5:54 ` [PATCH V10 15/17] powerpc/powernv: Allocate VF PE Wei Yang
2014-12-22 5:54 ` [PATCH V10 16/17] powerpc/powernv: Reserve additional space for IOV BAR, with m64_per_iov supported Wei Yang
2014-12-22 5:54 ` [PATCH V10 17/17] powerpc/powernv: Group VF PE when IOV BAR is big on PHB3 Wei Yang
2014-12-22 6:05 ` [PATCH V10 00/17] Enable SRIOV on Power8 Wei Yang
2015-01-13 18:05 ` Bjorn Helgaas
2015-01-15 2:27 ` [PATCH V11 " Wei Yang
2015-01-15 2:27 ` [PATCH V11 01/17] PCI/IOV: Export interface for retrieve VF's BDF Wei Yang
2015-02-20 23:09 ` Bjorn Helgaas
2015-03-02 6:05 ` Wei Yang
2015-01-15 2:27 ` [PATCH V11 02/17] PCI/IOV: add VF enable/disable hook Wei Yang
2015-02-10 0:26 ` Benjamin Herrenschmidt
2015-02-10 1:35 ` Wei Yang
2015-02-10 2:13 ` Benjamin Herrenschmidt
2015-02-10 6:18 ` Wei Yang
2015-01-15 2:27 ` [PATCH V11 03/17] PCI: Add weak pcibios_iov_resource_alignment() interface Wei Yang
2015-02-10 0:32 ` Benjamin Herrenschmidt
2015-02-10 1:44 ` Wei Yang
2015-01-15 2:27 ` [PATCH V11 04/17] PCI: Store VF BAR size in pci_sriov Wei Yang
2015-01-15 2:27 ` [PATCH V11 05/17] PCI: Take additional PF's IOV BAR alignment in sizing and assigning Wei Yang
2015-01-15 2:27 ` [PATCH V11 06/17] powerpc/pci: Add PCI resource alignment documentation Wei Yang
2015-02-04 23:44 ` Bjorn Helgaas
2015-02-10 1:02 ` Benjamin Herrenschmidt
2015-02-20 0:56 ` Bjorn Helgaas
2015-02-20 2:41 ` Benjamin Herrenschmidt
2015-01-15 2:27 ` [PATCH V11 07/17] powerpc/pci: Don't unset pci resources for VFs Wei Yang
2015-02-10 0:36 ` Benjamin Herrenschmidt
2015-02-10 1:51 ` Wei Yang
2015-02-10 2:14 ` Benjamin Herrenschmidt
2015-02-10 6:25 ` Wei Yang
2015-02-10 8:14 ` Benjamin Herrenschmidt
2015-02-20 23:47 ` Bjorn Helgaas
2015-03-02 6:09 ` Wei Yang
2015-01-15 2:27 ` [PATCH V11 08/17] powrepc/pci: Refactor pci_dn Wei Yang
2015-02-20 23:19 ` Bjorn Helgaas
2015-02-23 0:13 ` Gavin Shan
2015-02-24 8:13 ` Bjorn Helgaas [this message]
2015-02-24 8:25 ` Benjamin Herrenschmidt
2015-01-15 2:27 ` [PATCH V11 09/17] powerpc/pci: remove pci_dn->pcidev field Wei Yang
2015-01-15 2:28 ` [PATCH V11 10/17] powerpc/powernv: Use pci_dn in PCI config accessor Wei Yang
2015-01-15 2:28 ` [PATCH V11 11/17] powerpc/powernv: Allocate pe->iommu_table dynamically Wei Yang
2015-01-15 2:28 ` [PATCH V11 12/17] powerpc/powernv: Reserve additional space for IOV BAR according to the number of total_pe Wei Yang
2015-02-04 21:26 ` Bjorn Helgaas
2015-02-04 23:08 ` Wei Yang
2015-01-15 2:28 ` [PATCH V11 13/17] powerpc/powernv: Implement pcibios_iov_resource_alignment() on powernv Wei Yang
2015-02-04 21:26 ` Bjorn Helgaas
2015-02-04 22:45 ` Wei Yang
2015-01-15 2:28 ` [PATCH V11 14/17] powerpc/powernv: Shift VF resource with an offset Wei Yang
2015-01-30 23:08 ` Bjorn Helgaas
2015-02-03 1:30 ` Wei Yang
2015-02-03 7:01 ` [PATCH] powerpc/powernv: make sure the IOV BAR will not exceed limit after shifting Wei Yang
2015-02-04 0:19 ` Bjorn Helgaas
2015-02-04 3:34 ` Wei Yang
2015-02-04 14:19 ` Bjorn Helgaas
2015-02-04 15:20 ` Wei Yang
2015-02-04 16:08 ` [PATCH] pci/iov: fix memory leak introduced in "PCI: Store individual VF BAR size in struct pci_sriov" Wei Yang
2015-02-04 16:28 ` Bjorn Helgaas
2015-02-04 20:53 ` [PATCH] powerpc/powernv: make sure the IOV BAR will not exceed limit after shifting Bjorn Helgaas
2015-02-05 3:01 ` Wei Yang
2015-01-15 2:28 ` [PATCH V11 15/17] powerpc/powernv: Allocate VF PE Wei Yang
2015-01-15 2:28 ` [PATCH V11 16/17] powerpc/powernv: Reserve additional space for IOV BAR, with m64_per_iov supported Wei Yang
2015-02-04 22:05 ` Bjorn Helgaas
2015-02-05 0:07 ` Wei Yang
2015-01-15 2:28 ` [PATCH V11 17/17] powerpc/powernv: Group VF PE when IOV BAR is big on PHB3 Wei Yang
2015-02-04 23:44 ` [PATCH V11 00/17] Enable SRIOV on Power8 Bjorn Helgaas
2015-02-05 0:13 ` Wei Yang
2015-02-05 6:34 ` [PATCH 0/3] Code adjustment on pci/virtualization Wei Yang
2015-02-05 6:34 ` [PATCH 1/3] fix on Store individual VF BAR size in struct pci_sriov Wei Yang
2015-02-05 6:34 ` [PATCH 2/3] fix Reserve additional space for IOV BAR, with m64_per_iov supported Wei Yang
2015-02-05 6:34 ` [PATCH 3/3] remove the unused end in pnv_pci_vf_resource_shift() Wei Yang
2015-02-10 0:25 ` [PATCH V11 00/17] Enable SRIOV on Power8 Benjamin Herrenschmidt
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=20150224081330.GE6220@google.com \
--to=bhelgaas@google.com \
--cc=benh@au1.ibm.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=weiyang@linux.vnet.ibm.com \
/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).