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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 Sep 2021 00:38:10 +0000 From: "Tian, Kevin" <kevin.tian@...el.com> To: Jason Gunthorpe <jgg@...dia.com> CC: Alex Williamson <alex.williamson@...hat.com>, "Liu, Yi L" <yi.l.liu@...el.com>, "hch@....de" <hch@....de>, "jasowang@...hat.com" <jasowang@...hat.com>, "joro@...tes.org" <joro@...tes.org>, "jean-philippe@...aro.org" <jean-philippe@...aro.org>, "parav@...lanox.com" <parav@...lanox.com>, "lkml@...ux.net" <lkml@...ux.net>, "pbonzini@...hat.com" <pbonzini@...hat.com>, "lushenming@...wei.com" <lushenming@...wei.com>, "eric.auger@...hat.com" <eric.auger@...hat.com>, "corbet@....net" <corbet@....net>, "Raj, Ashok" <ashok.raj@...el.com>, "yi.l.liu@...ux.intel.com" <yi.l.liu@...ux.intel.com>, "Tian, Jun J" <jun.j.tian@...el.com>, "Wu, Hao" <hao.wu@...el.com>, "Jiang, Dave" <dave.jiang@...el.com>, "jacob.jun.pan@...ux.intel.com" <jacob.jun.pan@...ux.intel.com>, "kwankhede@...dia.com" <kwankhede@...dia.com>, "robin.murphy@....com" <robin.murphy@....com>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>, "dwmw2@...radead.org" <dwmw2@...radead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "baolu.lu@...ux.intel.com" <baolu.lu@...ux.intel.com>, "david@...son.dropbear.id.au" <david@...son.dropbear.id.au>, "nicolinc@...dia.com" <nicolinc@...dia.com> Subject: RE: [RFC 03/20] vfio: Add vfio_[un]register_device() > From: Jason Gunthorpe <jgg@...dia.com> > Sent: Thursday, September 23, 2021 7:52 AM > > On Wed, Sep 22, 2021 at 11:45:33PM +0000, Tian, Kevin wrote: > > > From: Alex Williamson <alex.williamson@...hat.com> > > > btw I realized another related piece regarding to the new layout that > > Jason suggested, which have sys device node include a link to the vfio > > devnode: > > > > /sys/bus/pci/devices/DDDD:BB:DD.F/vfio/vfioX/dev > > > > This for sure requires specific vfio driver support to get the link > > established. > > It doesn't. Just set the parent device of the vfio_device's struct > device to the physical struct device that vfio is already tracking - > ie the struct device providing the IOMMU. The driver core takes care > of everything else. > Thanks for correction. So it's still the same try-and-fail model for both devices which support iommufd and which do not.
Powered by blists - more mailing lists