On Wed, Dec 01, 2021 at 06:35:35PM +0100, Thomas Gleixner wrote: > On Wed, Dec 01 2021 at 09:00, Jason Gunthorpe wrote: > > On Wed, Dec 01, 2021 at 11:16:47AM +0100, Thomas Gleixner wrote: > >> Looking at the device slices as subdevices with their own struct device > >> makes a lot of sense from the conceptual level. > > > > Except IMS is not just for subdevices, it should be usable for any > > driver in any case as a general interrupt mechiansm, as you alluded to > > below about ethernet queues. ntb seems to be the current example of > > this need.. > > But NTB is operating through an abstraction layer and is not a direct > PCIe device driver. I'm not sure exactly how NTB seems to be split between switchtec and the ntb code, but since the ntbd code seems to be doing MMIO touches, it feels like part of a PCIe driver? > > IDXD is not so much making device "slices", but virtualizing and > > sharing a PCI device. The IDXD hardware is multi-queue like the NIC I > > described and the VFIO driver is simply allocating queues from a PCI > > device for specific usages and assigning them interrupts. > > Right. > > But what is the representation for that resulting device? Some VFIO > specific homebrewn muck or something which is based on struct device? Why is there a device? A queue is a queue, not a device. If the task is to make some struct device (eg mdev, or cdev, or whatever) then queues may be allocated to do this, but the queue is logically a resource handed out by the PCIe driver and there should not be a requirement to have an external struct device just to create a queue. > Right now with VF passthrough, I can see the interrupts which are > associated to the device. > > How is that going to be with something which is just made up? Does that > expose it's own msi properties then somewhere hidden in the VFIO layer? For sysfs, I think all interrupts should be on the PCI directory. > > There is already a char dev interface that equally allocates queues > > from the same IDXD device, why shouldn't it be able to access IMS > > interrupt pools too? > > Why wouldn't it be able to do so? The only 'struct device' there is a cdev and I really don't think cdevs should have interrupts. It is a bit hacky as a in-kernel thing and downright wrong as a sysfs ABI. > The VFIO driver does not own the irq chip ever. The irq chip is of > course part of the underlying infrastructure. I never asked for that. That isn't quite what I ment.. I ment the PCIe driver cannot create the domain or make use of the irq_chip until the VFIO layer comes along and provides the struct device. To me this is backwards layering, the interrupts come from the PCIe layer and should exist independently from VFIO. > When it allocates a slice for whatever usage then it also > allocates the IMS interrupts (though the VFIO people want to > have only one and do the allocations later on demand). > > That allocation cannot be part of the PCI/MSIx interrupt > domain as we already agreed on. Yes, it is just an open question of where the new irq_domain need to reside > 1) Storage > > A) Having "subdevices" solves the storage problem nicely and > makes everything just fall in place. Even for a purely > physical multiqueue device one can argue that each queue is a > "subdevice" of the physical device. The fact that we lump them > all together today is not an argument against that. I don't like the idea that queue is a device, that is trying to force a struct device centric world onto a queue which doesn't really want it.. > B) Requires extra storage in the PCIe device and extra storage > per subdevice, queue to keep track of the interrupts which > are associated to it. Yes > 2) Exposure of VFIO interrupts via sysfs > > A) Just works I would say this is flawed, in sysfs I expect all the interrupts for the PCIe device to be in the PCIe sysfs, not strewn over subsystem owned sub-directories. For instance, today in mlx5, when a subdevice allocates a queue for a slice (which is modeled as an aux device) the queue's assigned MSI-X interrupt shows up on the PCIe sysfs, not the aux. It should be uniform, if I assign a queue a legacy INT, MSI or an IMS it should show in sysfs in the same way. Leaking this kernel implementation detail as sysfs ABI does not seem good. > 3) On demand expansion of the vectors for VFIO > > A) Just works because the device has an irqdomain assigned. > > B) Requires extra indirections to do that Yes. > 4) PASID > > While an Intel IDXD specific issue, it want's to be solved > without any nasty hacks. > > A) Having a "subdevice" allows to associate the PASID with the > underlying struct device which makes IOMMU integration trivial > > B) Needs some other custom hackery to get that solved Yes > > Any possibility that the 'IMS' xarray could be outside the struct > > device? > > We could, but we really want to keep things tied to devices which is the > right thing to do. I see the sysfs issue makes this a poor idea as well, as where would the sysfs live if there was no struct device? I'm inclined to think either of your ideas with the xarray are good directions, primarily because it keeps HW data out of non-HW struct devices and maintains a consistent sysfs representation for all the different interrupt allocation methods. Regards, Jason
