On Sun, Feb 28, 2021 at 11:55 PM Leon Romanovsky <leon@xxxxxxxxxx> wrote: > > From: Leon Romanovsky <leonro@xxxxxxxxxx> > > @Alexander Duyck, please update me if I can add your ROB tag again > to the series, because you liked v6 more. > > Thanks > > --------------------------------------------------------------------------------- > Changelog > v7: > * Rebase on top v5.12-rc1 > * More english fixes > * Returned to static sysfs creation model as was implemented in v0/v1. Yeah, so I am not a fan of the series. The problem is there is only one driver that supports this, all VFs are going to expose this sysfs, and I don't know how likely it is that any others are going to implement this functionality. I feel like you threw out all the progress from v2-v6. I really feel like the big issue is that this model is broken as you have the VFs exposing sysfs interfaces that make use of the PFs to actually implement. Greg's complaint was the PF pushing sysfs onto the VFs. My complaint is VFs sysfs files operating on the PF. The trick is to find a way to address both issues. Maybe the compromise is to reach down into the IOV code and have it register the sysfs interface at device creation time in something like pci_iov_sysfs_link if the PF has the functionality present to support it. Also we might want to double check that the PF cannot be unbound while the VF is present. I know for a while there it was possible to remove the PF driver while the VF was present. The Mellanox drivers may not allow it but it might not hurt to look at taking a reference against the PF driver if you are allocating the VF MSI-X configuration sysfs file.
