> From: Koenig, Christian > Sent: Thursday, November 22, 2018 3:10 AM > > Am 21.11.18 um 12:16 schrieb Jean-Philippe Brucker: > > On 12/11/2018 14:40, Joerg Roedel wrote: > >> Hi Jean-Philippe, > >> > >> On Fri, Oct 19, 2018 at 07:11:54PM +0100, Jean-Philippe Brucker wrote: > >>> The allocator doesn't really belong in drivers/iommu because some > >>> drivers would like to allocate PASIDs for devices that aren't managed by > >>> an IOMMU, using the same ID space as IOMMU. It doesn't really > belong in > >>> drivers/pci either since platform device also support PASID. Add the > >>> allocator in drivers/base. > >> I don't really buy this argument, in the end it is the IOMMU that > >> enforces the PASID mappings for a device. Why should a device not > behind > >> an IOMMU need to allocate a pasid? Do you have examples of such > devices > >> which also don't have their own iommu built-in? > > I misunderstood that requirement. Reading through the thread again > > (https://www.mail-archive.com/iommu@lists.linux- > foundation.org/msg25640.html) > > it's more about a device using PASIDs as context IDs. Some contexts are > > not bound to processes but they still need their ID in the same PASID > > space as the contexts that are bound to process address spaces. So we > > can keep that code in drivers/iommu > > The problem with that approach is that we also need this allocator when > IOMMU is completely disabled. > > In other words PASIDs are used as contexts IDs by the hardware for > things like signaling which application has caused an interrupt/event > even when they are not used by IOMMU later on. > > Additional to that we have some MMUs which are internal to the devices > (GPUVM on AMD GPUs for example, similar exists for NVidia) which uses > PASIDs for address translation internally in the device. > > All of that is completely unrelated to IOMMU, but when IOMMU is enabled > you need to use the same allocator because all use cases use the same ID > space. >
imo context ID is a resource used by device internal while PASID is sth. informational to external world (as defined in PCI bus package). ideally two things are separate in hardware but can be associated (e.g. PASID as an optional parameter per context). That is what I know for Intel GPUs. For your device, is "PASIDs are used as contexts IDs" a software implementation policy or actual hardware requirement (i.e. no dedicated PASID recording)? Thanks Kevin _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu
