From: "Rustad, Mark D" <mark.d.rustad@intel.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>, "Daly, Dan" <dan.daly@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"Busch, Keith" <keith.busch@intel.com>,
"netanel@amazon.com" <netanel@amazon.com>,
"ddutile@redhat.com" <ddutile@redhat.com>,
"mheyne@amazon.de" <mheyne@amazon.de>,
"Wang, Liang-min" <liang-min.wang@intel.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"hch@lst.de" <hch@lst.de>,
"dwmw@amazon.co.uk" <dwmw@amazon.co.uk>
Subject: Re: [virtio-dev] [pci PATCH v7 1/5] pci: Add pci_sriov_configure_simple for PFs that don't manage VF resources
Date: Wed, 28 Mar 2018 21:30:29 +0000 [thread overview]
Message-ID: <C573B44F-097F-45D2-AB4C-B8BCCBCC2C4F@intel.com> (raw)
In-Reply-To: <20180315184055.3102.2435.stgit@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
On Mar 15, 2018, at 11:41 AM, Alexander Duyck <alexander.duyck@gmail.com> wrote:
> From: Alexander Duyck <alexander.h.duyck@intel.com>
>
> This patch adds a common configuration function called
> pci_sriov_configure_simple that will allow for managing VFs on devices
> where the PF is not capable of managing VF resources.
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
> ---
>
> v5: New patch replacing pci_sriov_configure_unmanaged with
> pci_sriov_configure_simple
> Dropped bits related to autoprobe changes
> v6: Defined pci_sriov_configure_simple as NULL if IOV is disabled
> v7: Updated pci_sriov_configure_simple to drop need for err value
> Fixed comment explaining why pci_sriov_configure_simple is NULL
>
> drivers/pci/iov.c | 31 +++++++++++++++++++++++++++++++
> include/linux/pci.h | 3 +++
> 2 files changed, 34 insertions(+)
Tested with the device identified in patch #2.
Tested-by: Mark Rustad <mark.d.rustad@intel.com>
--
Mark Rustad, Networking Division, Intel Corporation
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2018-03-28 21:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 18:40 [pci PATCH v7 0/5] Add support for unmanaged SR-IOV Alexander Duyck
2018-03-15 18:41 ` [pci PATCH v7 1/5] pci: Add pci_sriov_configure_simple for PFs that don't manage VF resources Alexander Duyck
2018-03-28 21:30 ` Rustad, Mark D [this message]
2018-03-15 18:42 ` [pci PATCH v7 2/5] virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices Alexander Duyck
2018-03-16 16:34 ` [virtio-dev] " Michael S. Tsirkin
2018-03-16 16:40 ` Alexander Duyck
2018-04-03 13:12 ` Michael S. Tsirkin
2018-04-03 17:32 ` Alexander Duyck
2018-04-03 18:27 ` Michael S. Tsirkin
2018-04-03 19:06 ` Alexander Duyck
2018-04-20 0:40 ` Michael S. Tsirkin
2018-04-20 14:56 ` Alexander Duyck
2018-04-20 15:28 ` Michael S. Tsirkin
2018-04-20 16:08 ` Alexander Duyck
2018-04-20 16:14 ` Michael S. Tsirkin
2018-04-21 7:05 ` Christoph Hellwig
2018-04-03 19:18 ` Rustad, Mark D
2018-03-28 21:31 ` Rustad, Mark D
2018-04-03 13:11 ` [virtio-dev] " Michael S. Tsirkin
2018-03-15 18:43 ` [pci PATCH v7 3/5] ena: Migrate over to unmanaged SR-IOV support Alexander Duyck
2018-03-15 18:43 ` [pci PATCH v7 4/5] nvme: " Alexander Duyck
2018-03-15 18:44 ` [pci PATCH v7 5/5] pci-pf-stub: Add PF driver stub for PFs that function only to enable VFs Alexander Duyck
2018-03-16 21:42 ` [pci PATCH v7 0/5] Add support for unmanaged SR-IOV Don Dutile
2018-04-19 22:54 ` Alexander Duyck
2018-04-20 0:46 ` Michael S. Tsirkin
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=C573B44F-097F-45D2-AB4C-B8BCCBCC2C4F@intel.com \
--to=mark.d.rustad@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=dan.daly@intel.com \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=dwmw@amazon.co.uk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=kvm@vger.kernel.org \
--cc=liang-min.wang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=mheyne@amazon.de \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=virtio-dev@lists.oasis-open.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).