> From: Jason Gunthorpe <jgg@xxxxxxxxxx> > Sent: Thursday, September 23, 2021 8:07 PM > > On Thu, Sep 23, 2021 at 09:14:58AM +0000, Tian, Kevin wrote: > > > currently the type is aimed to differentiate three usages: > > > > - kernel-managed I/O page table > > - user-managed I/O page table > > - shared I/O page table (e.g. with mm, or ept) > > Creating a shared ios is something that should probably be a different > command. why? I didn't understand the criteria here... > > > we can remove 'type', but is FORMAT_KENREL/USER/SHARED a good > > indicator? their difference is not about format. > > Format should be > > FORMAT_KERNEL/FORMAT_INTEL_PTE_V1/FORMAT_INTEL_PTE_V2/etc INTEL_PTE_V1/V2 are formats. Why is kernel-managed called a format? > > > Dave's links didn't answer one puzzle from me. Does PPC needs accurate > > range information or be ok with a large range including holes (then let > > the kernel to figure out where the holes locate)? > > My impression was it only needed a way to select between the two > different cases as they are exclusive. I'd see this API as being a > hint and userspace should query the exact ranges to learn what was > actually created. yes, the user can query the permitted range using DEVICE_GET_INFO. But in the end if the user wants two separate regions, I'm afraid that the underlying iommu driver wants to know the exact info. iirc PPC has one global system address space shared by all devices. It is possible that the user may want to claim range-A and range-C, with range-B in-between but claimed by another user. Then simply using one hint range [A-lowend, C-highend] might not work. > > > > device-specific escape if more specific customization is needed and is > > > needed to specify user space page tables anyhow. > > > > and I didn't understand the 2nd link. How does user-managed page > > table jump into this range claim problem? I'm getting confused... > > PPC could also model it using a FORMAT_KERNEL_PPC_X, > FORMAT_KERNEL_PPC_Y > though it is less nice.. yes PPC can use different format, but I didn't understand why it is related user-managed page table which further requires nesting. sound disconnected topics here... > > > > Yes, ioas_id should always be the xarray index. > > > > > > PASID needs to be called out as PASID or as a generic "hw description" > > > blob. > > > > ARM doesn't use PASID. So we need a generic blob, e.g. ioas_hwid? > > ARM *does* need PASID! PASID is the label of the DMA on the PCI bus, > and it MUST be exposed in that format to be programmed into the PCI > device itself. In the entire discussion in previous design RFC, I kept an impression that ARM-equivalent PASID is called SSID. If we can use PASID as a general term in iommufd context, definitely it's much better! > > All of this should be able to support a userspace, like DPDK, creating > a PASID on its own without any special VFIO drivers. > > - Open iommufd > - Attach the vfio device FD > - Request a PASID device id > - Create an ios against the pasid device id > - Query the ios for the PCI PASID # > - Program the HW to issue TLPs with the PASID this all makes me very confused, and completely different from what we agreed in previous v2 design proposal: - open iommufd - create an ioas - attach vfio device to ioasid, with vPASID info * vfio converts vPASID to pPASID and then call iommufd_device_attach_ioasid() * the latter then installs ioas to the IOMMU with RID/PASID > > > and still we have both ioas_id (iommufd) and ioasid (ioasid.c) in the > > kernel. Do we want to clear this confusion? Or possibly it's fine because > > ioas_id is never used outside of iommufd and iommufd doesn't directly > > call ioasid_alloc() from ioasid.c? > > As long as it is ioas_id and ioasid it is probably fine.. let's align with others in a few hours. > > > > kvm's API to program the vPASID translation table should probably take > > > in a (iommufd,ioas_id,device_id) tuple and extract the IOMMU side > > > information using an in-kernel API. Userspace shouldn't have to > > > shuttle it around. > > > > the vPASID info is carried in VFIO_DEVICE_ATTACH_IOASID uAPI. > > when kvm calls iommufd with above tuple, vPASID->pPASID is > > returned to kvm. So we still need a generic blob to represent > > vPASID in the uAPI. > > I think you have to be clear about what the value is being used > for. Is it an IOMMU page table handle or is it a PCI PASID value? > > AFAICT I think it is the former in the Intel scheme as the "vPASID" is > really about presenting a consistent IOMMU handle to the guest across > migration, it is not the value that shows up on the PCI bus. > It's the former. But vfio driver needs to maintain vPASID->pPASID translation in the mediation path, since what guest programs is vPASID. Thanks Kevin
