> From: Jason Gunthorpe <j...@nvidia.com> > Sent: Friday, December 10, 2021 8:40 PM > > > > Then Qemu needs to find out the GSI number for the vIRTE handle. > > Again Qemu doesn't have such information since it doesn't know > > which MSI[-X] entry points to this handle due to no trap. > > No this is already going wrong. qemu *cannot* know the MSI information > because there is no MSI information for IMS.
I haven't thought of IMS at this step. The IR approach applies to all types of interrupt storages, thus I'm more interested in how it affect the storages which are already virtualized today (MSI[-X] in my thought practice). > > All qemu should get is the origin device information and data about > how the guest wants the interrupt setup. yes, this is what I concluded in previous mail. The hypercall should provide those information to the host and then get addr/data pair back from the host. > > Forget about guests and all of this complexity, design how to make > VFIO work with IMS in pure userspace like DPDK. > > We must have a VFIO ioctl to acquire a addr/data pair and link it to > an event fd. No question on it. Still need more thought down this road. Thanks Kevin _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
