From: David Woodhouse <dwmw2@infradead.org>
To: Don Dutile <ddutile@redhat.com>,
Alexander Duyck <alexander.duyck@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pci <linux-pci@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alexander Duyck <alexander.h.duyck@intel.com>,
"Bryant G. Ly" <bryantly@linux.vnet.ibm.com>,
Bodong Wang <bodong@mellanox.com>,
Alex Williamson <alex.williamson@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] uio/uio_pci_generic: Add SR-IOV support
Date: Thu, 28 Sep 2017 16:52:26 +0100 [thread overview]
Message-ID: <1506613946.7476.130.camel@infradead.org> (raw)
In-Reply-To: <7bbb6cce-3462-fbb2-9ae4-5c08ab2b01b4@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Thu, 2017-09-28 at 11:05 -0400, Don Dutile wrote:
> ah, nickel summary: no in-kernel driver w/.sriov-configure method.
> if so, now I'm up to speed with you....
> hmmmm....
> so, that would imply we need an in-kernel, pcie-common, .sriov-
> configure method
> that's invoked if a driver isn't bound to a device? ... yes?
Well that was kind of the point in my question below the ---
Is that something we want to be generic? Would we want to have quirks
for the devices where we might *not* want it?
Anything that *has* a driver for the PF, should have .sriov_configure
already. Anything that doesn't have a driver can (now) use UIO to
enable SR-IOV. So we don't *have* to make it unconditionally
available...
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
next prev parent reply other threads:[~2017-09-28 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 12:59 [PATCH] uio/uio_pci_generic: Add SR-IOV support David Woodhouse
2017-09-27 22:00 ` Bjorn Helgaas
2017-09-27 22:20 ` David Woodhouse
2017-09-27 23:06 ` Alexander Duyck
2017-09-28 12:22 ` Don Dutile
2017-09-28 13:46 ` David Woodhouse
2017-09-28 15:05 ` Don Dutile
2017-09-28 15:52 ` David Woodhouse [this message]
2017-09-28 16:56 ` Don Dutile
2017-10-02 12:35 ` David Woodhouse
2017-10-02 18:52 ` Don Dutile
2017-10-02 19:10 ` David Woodhouse
2017-10-02 22:02 ` Don Dutile
2017-09-28 12:12 ` Don Dutile
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=1506613946.7476.130.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=bodong@mellanox.com \
--cc=bryantly@linux.vnet.ibm.com \
--cc=ddutile@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.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).