[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1520953463.20126.15.camel@infradead.org>
Date: Tue, 13 Mar 2018 15:04:23 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Alexander Duyck <alexander.duyck@...il.com>,
Don Dutile <ddutile@...hat.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
"Duyck, Alexander H" <alexander.h.duyck@...el.com>,
linux-pci@...r.kernel.org, virtio-dev@...ts.oasis-open.org,
kvm@...r.kernel.org, Netdev <netdev@...r.kernel.org>,
"Daly, Dan" <dan.daly@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-nvme@...ts.infradead.org,
Keith Busch <keith.busch@...el.com>, netanel@...zon.com,
Maximilian Heyne <mheyne@...zon.de>,
"Wang, Liang-min" <liang-min.wang@...el.com>,
"Rustad, Mark D" <mark.d.rustad@...el.com>,
Christoph Hellwig <hch@....de>
Subject: Re: [pci PATCH v5 3/4] ena: Migrate over to unmanaged SR-IOV
support
On Tue, 2018-03-13 at 07:51 -0700, Alexander Duyck wrote:
> Actually the suggestion I had from Don Dutile was that we should be
> looking at creating a pci-stub like driver specifically for those type
> of devices, but without the ability to arbitrarily assign devices.
> Basically we have to white-list it in one device at a time for those
> kind of things.
It's still not clear what the point of that would be.
> If you have the device ID of the thing you wanted to have work with
> pci-stub before I could look at putting together a quick driver and
> adding it to this set.
1d0f:0053 would be an example.
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5213 bytes)
Powered by blists - more mailing lists