LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <firstname.lastname@example.org> To: Alexander Duyck <email@example.com> Cc: "Daly, Dan" <firstname.lastname@example.org>, Bjorn Helgaas <email@example.com>, "Duyck, Alexander H" <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, Netdev <firstname.lastname@example.org>, LKML <email@example.com>, firstname.lastname@example.org, Keith Busch <email@example.com>, firstname.lastname@example.org, Don Dutile <email@example.com>, Maximilian Heyne <firstname.lastname@example.org>, "Wang, Liang-min" <email@example.com>, "Rustad, Mark D" <firstname.lastname@example.org>, David Woodhouse <email@example.com>, Christoph Hellwig <firstname.lastname@example.org>, email@example.com Subject: Re: [virtio-dev] [pci PATCH v7 2/5] virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices Date: Fri, 20 Apr 2018 03:40:55 +0300 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAKgT0Ude79FYrK4qA0OKRJ1NackyqPi-hZ8Zh3WSdLDFxoOosQ@mail.gmail.com> On Tue, Apr 03, 2018 at 12:06:03PM -0700, Alexander Duyck wrote: > On Tue, Apr 3, 2018 at 11:27 AM, Michael S. Tsirkin <email@example.com> wrote: > > On Tue, Apr 03, 2018 at 10:32:00AM -0700, Alexander Duyck wrote: > >> On Tue, Apr 3, 2018 at 6:12 AM, Michael S. Tsirkin <firstname.lastname@example.org> wrote: > >> > On Fri, Mar 16, 2018 at 09:40:34AM -0700, Alexander Duyck wrote: > >> >> On Fri, Mar 16, 2018 at 9:34 AM, Michael S. Tsirkin <email@example.com> wrote: > >> >> > On Thu, Mar 15, 2018 at 11:42:41AM -0700, Alexander Duyck wrote: > >> >> >> From: Alexander Duyck <firstname.lastname@example.org> > >> >> >> > >> >> >> Hardware-realized virtio_pci devices can implement SR-IOV, so this > >> >> >> patch enables its use. The device in question is an upcoming Intel > >> >> >> NIC that implements both a virtio_net PF and virtio_net VFs. These > >> >> >> are hardware realizations of what has been up to now been a software > >> >> >> interface. > >> >> >> > >> >> >> The device in question has the following 4-part PCI IDs: > >> >> >> > >> >> >> PF: vendor: 1af4 device: 1041 subvendor: 8086 subdevice: 15fe > >> >> >> VF: vendor: 1af4 device: 1041 subvendor: 8086 subdevice: 05fe > >> >> >> > >> >> >> The patch currently needs no check for device ID, because the callback > >> >> >> will never be made for devices that do not assert the capability or > >> >> >> when run on a platform incapable of SR-IOV. > >> >> >> > >> >> >> One reason for this patch is because the hardware requires the > >> >> >> vendor ID of a VF to be the same as the vendor ID of the PF that > >> >> >> created it. So it seemed logical to simply have a fully-functioning > >> >> >> virtio_net PF create the VFs. This patch makes that possible. > >> >> >> > >> >> >> Reviewed-by: Christoph Hellwig <email@example.com> > >> >> >> Signed-off-by: Mark Rustad <firstname.lastname@example.org> > >> >> >> Signed-off-by: Alexander Duyck <email@example.com> > >> >> > > >> >> > So if and when virtio PFs can manage the VFs, then we can > >> >> > add a feature bit for that? > >> >> > Seems reasonable. > >> >> > >> >> Yes. If nothing else you may not even need a feature bit depending on > >> >> how things go. > >> > > >> > OTOH if the interface is changed in an incompatible way, > >> > and old Linux will attempt to drive the new device > >> > since there is no check. > >> > > >> > I think we should add a feature bit right away. > >> > >> I'm not sure why you would need a feature bit. The capability is > >> controlled via PCI configuration space. If it is present the device > >> has the capability. If it is not then it does not. > >> > >> Basically if the PCI configuration space is not present then the sysfs > >> entries will not be spawned and nothing will attempt to use this > >> function. > >> > >> - ALex > > > > It's about compability with older guests which ignore the > > capability. > > > > The feature is thus helpful so host knows whether guest supports VFs. > > The thing is if the capability is ignored then the feature isn't used. > So for SR-IOV it isn't an uncommon thing for there to be drivers for > the PF floating around that do not support SR-IOV. In such cases > SR-IOV just isn't used while the hardware could support it. Right but how come there are VF drivers but PF driver does not know about these? And are there PF drivers that intentially do not enable SRIOV because it's known to be broken in some way? Case in point I do think virtio want to limit this depending on a feature bit on general principles (the principle being that all extensions have feature bits). There are security implications here - we previously relied on whitelisting after all. Wouldn't it be safer to be a bit more careful and update the actual PF drivers? It's just one line per driver, but it can be done with an ack by driver maintainer. If/once we find out all drivers do have it, we can then change the default. > I would think in the case of virtio it would be the same kind of > thing. Basically if SR-IOV is supported by the host then the > capability would be present. If SR-IOV is supported by the guest then > it would make use of the capability to spawn VFs. If either the > capability isn't present, or the driver doesn't use it then you won't > be able to spawn VFs in the guest. > Maybe I am missing something. Do you support dynamically changing the > PCI configuration space for Virtio devices based on the presence of > feature bits provided by the guest? No. The point is that IMHO at least virtio - in absence of feature bit - to ignore VFs rather than assume they are safe to drive in an unmanaged way. > Also are you saying this patch set should wait on the feature bit to > be added, or are you talking about doing this as some sort of > follow-up? > > - Alex I think for virtio it should include the feature bit, yes. Adding feature bit is very easy - post a patch to the virtio TC mailing list, wait about a week to give people time to respond (two weeks if it is around holidays and such). -- MST
next prev parent reply other threads:[~2018-04-20 0:41 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 ` [virtio-dev] " Rustad, Mark D 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 [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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: linkBe 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).