From: Alex Williamson <alex.williamson@redhat.com>
To: "Wang, Liang-min" <liang-min.wang@intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"O'riordain, Seosamh" <seosamh.oriordain@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] Enable SR-IOV instantiation through /sys file
Date: Mon, 6 Nov 2017 16:27:13 -0700 [thread overview]
Message-ID: <20171106162713.0a49ac3f@t450s.home> (raw)
In-Reply-To: <B6CB929FEBC10D4FAC4BCA7EF2298E259DB5BB50@FMSMSX110.amr.corp.intel.com>
On Tue, 31 Oct 2017 12:55:20 +0000
"Wang, Liang-min" <liang-min.wang@intel.com> wrote:
> > -----Original Message-----
> > From: David Woodhouse [mailto:dwmw2@infradead.org]
> > Sent: Monday, October 30, 2017 8:39 AM
> > To: Christoph Hellwig <hch@infradead.org>; Duyck, Alexander H
> > <alexander.h.duyck@intel.com>
> > Cc: Wang, Liang-min <liang-min.wang@intel.com>;
> > alex.williamson@redhat.com; linux-kernel@vger.kernel.org; Kirsher, Jeffrey T
> > <jeffrey.t.kirsher@intel.com>; kvm@vger.kernel.org; bhelgaas@google.com;
> > linux-pci@vger.kernel.org
> > Subject: Re: [PATCH] Enable SR-IOV instantiation through /sys file
> >
> > On Sat, 2017-10-28 at 23:16 -0700, Christoph Hellwig wrote:
> > > On Fri, Oct 27, 2017 at 11:20:41PM +0000, Duyck, Alexander H wrote:
> > > >
> > > > I don't see this so much as a security problem per-se. It all depends
> > > > on the hardware setup. If I recall correctly, there are devices where
> > > > the PF function doesn't really do much other than act as a bit more
> > > > heavy-weight VF, and the actual logic is handled by a firmware engine
> > > > on the device.
> > >
> > > Can you cite an example? While those surely could exist in theory,
> > > I can't think of a practical example.
> >
> > I have them, which is why I'm patching the UIO driver to allow num_vfs
> > to be set. I don't even want to *use* the UIO driver for any purpose
> > except to make that appear in sysfs. It's all handled in the device.
> >
> > (I think we might be able to just give the PF out to a guest as if it
> > were just another VF, but I don't think we actually *do* that right
> > now).
>
> Under UEFI secure boot environment, kernel puts restrictions on UIO and its derivatives.
> So, user-space function/driver based upon UIO is no longer working under UEFI secure
> boot environment. The next viable option is vfio-pci, hence this patch in parallel with
> UIO work.
If you want a PF driver that does nothing other than allow SR-IOV to be
enabled, doesn't that scream pci-stub? Trying to overlay it onto a
driver that also allows userspace driver access to that device seems
like the worst idea. Thanks,
Alex
next prev parent reply other threads:[~2017-11-06 23:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 20:04 [PATCH] Enable SR-IOV instantiation through /sys file Jeff Kirsher
2017-10-24 21:43 ` Alex Williamson
2017-10-24 21:49 ` Wang, Liang-min
2017-10-24 22:06 ` Alex Williamson
2017-10-24 22:29 ` Wang, Liang-min
2017-10-25 8:39 ` Alex Williamson
2017-10-27 21:50 ` Wang, Liang-min
2017-10-27 22:19 ` Alex Williamson
2017-10-27 22:30 ` Wang, Liang-min
2017-10-27 23:20 ` Duyck, Alexander H
2017-10-29 6:16 ` Christoph Hellwig
2017-10-29 21:12 ` Alexander Duyck
2017-10-30 12:39 ` David Woodhouse
2017-10-31 12:55 ` Wang, Liang-min
2017-11-06 23:27 ` Alex Williamson [this message]
2017-11-06 23:47 ` Alexander Duyck
2017-11-07 16:59 ` Alex Williamson
2017-11-06 19:55 ` Bjorn Helgaas
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=20171106162713.0a49ac3f@t450s.home \
--to=alex.williamson@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=dwmw2@infradead.org \
--cc=hch@infradead.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kvm@vger.kernel.org \
--cc=liang-min.wang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seosamh.oriordain@intel.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).