lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 12 Nov 2020 09:10:26 -0400 From: Jason Gunthorpe <jgg@...dia.com> To: "Raj, Ashok" <ashok.raj@...el.com> CC: Thomas Gleixner <tglx@...utronix.de>, Christoph Hellwig <hch@...radead.org>, David Woodhouse <dwmw2@...radead.org>, Dan Williams <dan.j.williams@...el.com>, "Tian, Kevin" <kevin.tian@...el.com>, "Jiang, Dave" <dave.jiang@...el.com>, Bjorn Helgaas <helgaas@...nel.org>, "vkoul@...nel.org" <vkoul@...nel.org>, "Dey, Megha" <megha.dey@...el.com>, "maz@...nel.org" <maz@...nel.org>, "bhelgaas@...gle.com" <bhelgaas@...gle.com>, "alex.williamson@...hat.com" <alex.williamson@...hat.com>, "Pan, Jacob jun" <jacob.jun.pan@...el.com>, "Liu, Yi L" <yi.l.liu@...el.com>, "Lu, Baolu" <baolu.lu@...el.com>, "Kumar, Sanjay K" <sanjay.k.kumar@...el.com>, "Luck, Tony" <tony.luck@...el.com>, "jing.lin@...el.com" <jing.lin@...el.com>, "kwankhede@...dia.com" <kwankhede@...dia.com>, "eric.auger@...hat.com" <eric.auger@...hat.com>, "parav@...lanox.com" <parav@...lanox.com>, "rafael@...nel.org" <rafael@...nel.org>, "netanelg@...lanox.com" <netanelg@...lanox.com>, "shahafs@...lanox.com" <shahafs@...lanox.com>, "yan.y.zhao@...ux.intel.com" <yan.y.zhao@...ux.intel.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>, "Ortiz, Samuel" <samuel.ortiz@...el.com>, "Hossain, Mona" <mona.hossain@...el.com>, "dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org> Subject: Re: [PATCH v4 06/17] PCI: add SIOV and IMS capability detection On Wed, Nov 11, 2020 at 03:03:21PM -0800, Raj, Ashok wrote: > By default the DVSEC is not presented to guest even when the full PF is > presented to guest. I believe VFIO only builds and presents known standard > capabilities and specific extended capabilities. I'm a bit weak but maybe > @AlexWilliamson can confirm if I'm off track. This also need to work on Hyper-V and all other cases, you can't just assume everything is vfio and kvm. It is horrible to ask people to go back an retroactively change their config space in a device just to work around all the design failings Thomas eloquantly describes :( Jason
Powered by blists - more mailing lists