From: Bjorn Helgaas <bhelgaas@google.com>
To: Wei Yang <weiyang@linux.vnet.ibm.com>
Cc: benh@au1.ibm.com, gwshan@linux.vnet.ibm.com,
linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V14 00/21] Enable SRIOV on Power8
Date: Fri, 20 Mar 2015 16:20:45 -0500 [thread overview]
Message-ID: <20150320212045.GL26935@google.com> (raw)
In-Reply-To: <1426820797-6267-1-git-send-email-weiyang@linux.vnet.ibm.com>
On Fri, Mar 20, 2015 at 11:06:16AM +0800, Wei Yang wrote:
> This patchset enables the SRIOV on POWER8.
>
> The general idea is put each VF into one individual PE and allocate required
> resources like MMIO/DMA/MSI. The major difficulty comes from the MMIO
> allocation and adjustment for PF's IOV BAR.
>
> On P8, we use M64BT to cover a PF's IOV BAR, which could make an individual VF
> sit in its own PE. This gives more flexiblity, while at the mean time it
> brings on some restrictions on the PF's IOV BAR size and alignment.
For patches 03-12 (the "PCI: " ones):
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
It's fine if you want to take all these via the powerpc tree. I don't see
much if anything in my queue that will conflict with them.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <bhelgaas@google.com>
To: Wei Yang <weiyang@linux.vnet.ibm.com>
Cc: linux-pci@vger.kernel.org, benh@au1.ibm.com,
linuxppc-dev@lists.ozlabs.org, gwshan@linux.vnet.ibm.com
Subject: Re: [PATCH V14 00/21] Enable SRIOV on Power8
Date: Fri, 20 Mar 2015 16:20:45 -0500 [thread overview]
Message-ID: <20150320212045.GL26935@google.com> (raw)
In-Reply-To: <1426820797-6267-1-git-send-email-weiyang@linux.vnet.ibm.com>
On Fri, Mar 20, 2015 at 11:06:16AM +0800, Wei Yang wrote:
> This patchset enables the SRIOV on POWER8.
>
> The general idea is put each VF into one individual PE and allocate required
> resources like MMIO/DMA/MSI. The major difficulty comes from the MMIO
> allocation and adjustment for PF's IOV BAR.
>
> On P8, we use M64BT to cover a PF's IOV BAR, which could make an individual VF
> sit in its own PE. This gives more flexiblity, while at the mean time it
> brings on some restrictions on the PF's IOV BAR size and alignment.
For patches 03-12 (the "PCI: " ones):
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
It's fine if you want to take all these via the powerpc tree. I don't see
much if anything in my queue that will conflict with them.
Bjorn
next prev parent reply other threads:[~2015-03-20 21:20 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 3:06 [PATCH V14 00/21] Enable SRIOV on Power8 Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 01/21] powerpc/pci: Refactor pci_dn Wei Yang
2015-03-20 3:06 ` [PATCH V14 02/21] powerpc/powernv: Use pci_dn, not device_node, in PCI config accessor Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 03/21] PCI: Print more info in sriov_enable() error message Wei Yang
2015-03-20 3:06 ` [PATCH V14 04/21] PCI: Print PF SR-IOV resource that contains all VF(n) BAR space Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 05/21] PCI: Keep individual VF BAR size in struct pci_sriov Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 06/21] PCI: Index IOV resources in the conventional style Wei Yang
2015-03-20 3:06 ` [PATCH V14 07/21] PCI: Refresh First VF Offset and VF Stride when updating NumVFs Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 08/21] PCI: Calculate maximum number of buses required for VFs Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 09/21] PCI: Export pci_iov_virtfn_bus() and pci_iov_virtfn_devfn() Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 10/21] PCI: Add pcibios_sriov_enable() and pcibios_sriov_disable() Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 5:46 ` Gavin Shan
2015-03-20 5:46 ` Gavin Shan
2015-03-20 3:06 ` [PATCH V14 11/21] PCI: Add pcibios_iov_resource_alignment() interface Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 12/21] PCI: Consider additional PF's IOV BAR alignment in sizing and assigning Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 13/21] powerpc/pci: Don't unset PCI resources for VFs Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 14/21] powerpc/powernv: Allocate struct pnv_ioda_pe iommu_table dynamically Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 21:22 ` Bjorn Helgaas
2015-03-20 21:22 ` Bjorn Helgaas
2015-03-20 3:06 ` [PATCH V14 15/21] powerpc/powernv: Reserve additional space for IOV BAR according to the number of total_pe Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 16/21] powerpc/powernv: Implement pcibios_iov_resource_alignment() on powernv Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 17/21] powerpc/powernv: Shift VF resource with an offset Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-23 23:22 ` Daniel Axtens
2015-03-23 23:22 ` Daniel Axtens
2015-03-24 1:54 ` Wei Yang
2015-03-24 1:54 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 18/21] powerpc/powernv: Reserve additional space for IOV BAR, with m64_per_iov supported Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 19/21] powerpc/powernv: Group VF PE when IOV BAR is big on PHB3 Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 20/21] powerpc/pci: Remove unused struct pci_dn.pcidev field Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 3:06 ` [PATCH V14 21/21] powerpc/pci: Add PCI resource alignment documentation Wei Yang
2015-03-20 3:06 ` Wei Yang
2015-03-20 5:43 ` [PATCH V14 00/21] Enable SRIOV on Power8 Gavin Shan
2015-03-20 5:43 ` Gavin Shan
2015-03-20 14:34 ` Bjorn Helgaas
2015-03-20 14:34 ` Bjorn Helgaas
2015-03-20 21:05 ` Benjamin Herrenschmidt
2015-03-20 21:05 ` Benjamin Herrenschmidt
2015-03-20 21:16 ` Bjorn Helgaas
2015-03-20 21:16 ` Bjorn Helgaas
2015-03-20 21:28 ` Benjamin Herrenschmidt
2015-03-20 21:28 ` Benjamin Herrenschmidt
2015-03-20 21:20 ` Bjorn Helgaas [this message]
2015-03-20 21:20 ` Bjorn Helgaas
2015-03-20 22:24 ` Wei Yang
2015-03-20 22:24 ` Wei Yang
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=20150320212045.GL26935@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.