On Wed, 13 Sep 2023 16:29:30 +0200 Thomas Hellström <thomas.hellstrom@xxxxxxxxxxxxxxx> wrote: > On 9/13/23 16:01, Boris Brezillon wrote: > > On Wed, 13 Sep 2023 15:22:56 +0200 > > Thomas Hellström <thomas.hellstrom@xxxxxxxxxxxxxxx> wrote: > > > >> On 9/13/23 13:33, Boris Brezillon wrote: > >>> On Wed, 13 Sep 2023 12:39:01 +0200 > >>> Thomas Hellström <thomas.hellstrom@xxxxxxxxxxxxxxx> wrote: > >>> > >>>> Hi, > >>>> > >>>> On 9/13/23 09:19, Boris Brezillon wrote: > >>>>> On Wed, 13 Sep 2023 17:05:42 +1000 > >>>>> Dave Airlie <airlied@xxxxxxxxx> wrote: > >>>>> > >>>>>> On Wed, 13 Sept 2023 at 17:03, Boris Brezillon > >>>>>> <boris.brezillon@xxxxxxxxxxxxx> wrote: > >>>>>>> On Tue, 12 Sep 2023 18:20:32 +0200 > >>>>>>> Thomas Hellström <thomas.hellstrom@xxxxxxxxxxxxxxx> wrote: > >>>>>>> > >>>>>>>>> +/** > >>>>>>>>> + * get_next_vm_bo_from_list() - get the next vm_bo element > >>>>>>>>> + * @__gpuvm: The GPU VM > >>>>>>>>> + * @__list_name: The name of the list we're iterating on > >>>>>>>>> + * @__local_list: A pointer to the local list used to store already iterated items > >>>>>>>>> + * @__prev_vm_bo: The previous element we got from drm_gpuvm_get_next_cached_vm_bo() > >>>>>>>>> + * > >>>>>>>>> + * This helper is here to provide lockless list iteration. Lockless as in, the > >>>>>>>>> + * iterator releases the lock immediately after picking the first element from > >>>>>>>>> + * the list, so list insertion deletion can happen concurrently. > >>>>>>>> Are the list spinlocks needed for that async state update from within > >>>>>>>> the dma-fence critical section we've discussed previously? > >>>>>>> Any driver calling _[un]link() from its drm_gpu_scheduler::run_job() > >>>>>>> hook will be in this situation (Panthor at the moment, PowerVR soon). I > >>>>>>> get that Xe and Nouveau don't need that because they update the VM > >>>>>>> state early (in the ioctl path), but I keep thinking this will hurt us > >>>>>>> if we don't think it through from the beginning, because once you've > >>>>>>> set this logic to depend only on resv locks, it will be pretty hard to > >>>>>>> get back to a solution which lets synchronous VM_BINDs take precedence > >>>>>>> on asynchronous request, and, with vkQueueBindSparse() passing external > >>>>>>> deps (plus the fact the VM_BIND queue might be pretty deep), it can > >>>>>>> take a long time to get your synchronous VM_BIND executed... > >>>> So this would boil down to either (possibly opt-in) keeping the spinlock > >>>> approach or pushing the unlink out to a wq then? > >>> Deferred _unlink() would not be an issue, since I already defer the > >>> drm_gpuva destruction to a wq, it would just a be a matter of moving the > >>> _unlink() call there as well. But _link() also takes the GEM gpuva list > >>> lock, and that one is bit tricky, in that sm_map() can trigger 2 more > >>> _link() calls for the prev/next mappings, which we can't guess until we > >>> get to execute the VM update. If we mandate the use of the GEM resv > >>> lock, that simply means async VM updates (AKA calling > >>> drm_gpuvm_sm_[un]map()) are not an option. And if this is what everyone > >>> agrees on, then I'd like the APIs that make this sort of async VM > >>> update possible (drm_gpuvm_sm_[un]map(), the drm_gpuvm_ops::sm_step* > >>> methods, and probably other things) to be dropped, so we don't make it > >>> look like it's something we support. > >>> > >>>> BTW, as also asked in a reply to Danilo, how do you call unlink from > >>>> run_job() when it was requiring the obj->dma_resv lock, or was that a WIP? > >>> _unlink() makes sure the GEM gpuva list lock is taken, but this can be > >>> a custom lock (see drm_gem_gpuva_set_lock()). In panthor we have > >>> panthor_gem_object::gpuva_list_lock that's dedicated the gpuva list > >>> protection. We make sure we never take this lock while allocating > >>> memory to guarantee the dma-signalling path can't deadlock. > >>> > >>>>>>> > >>>>>> btw what is the use case for this? do we have actual vulkan > >>>>>> applications we know will have problems here? > >>>>> I don't, but I think that's a concern Faith raised at some point (dates > >>>>> back from when I was reading threads describing how VM_BIND on i915 > >>>>> should work, and I was clearly discovering this whole VM_BIND thing at > >>>>> that time, so maybe I misunderstood). > >>>>> > >>>>>> it feels like a bit of premature optimisation, but maybe we have use cases. > >>>>> Might be, but that's the sort of thing that would put us in a corner if > >>>>> we don't have a plan for when the needs arise. Besides, if we don't > >>>>> want to support that case because it's too complicated, I'd recommend > >>>>> dropping all the drm_gpuvm APIs that let people think this mode is > >>>>> valid/supported (map/remap/unmap hooks in drm_gpuvm_ops, > >>>>> drm_gpuvm_sm_[un]map helpers, etc). Keeping them around just adds to the > >>>>> confusion. > >>>> Xe allows bypassing the bind-queue with another bind-queue, but to > >>>> completely avoid dependencies between queues the Operations may not > >>>> overlap. > >>> So, you check the VM state with some VM lock held (would be the VM resv > >>> in my case), and if the mapping is new (no overlaps with pre-existing > >>> mappings), you queue it to the fast-track/sync-VM_BIND queue. What would > >>> be missing I guess is a way to know if the mapping is active (MMU has > >>> been updated) or pending (MMU update queued to the bind-queue), so I can > >>> fast-track mapping/unmapping of active mappings. This would leave > >>> overlapping sync/async VM updates, which can't happen in practice > >>> unless userspace is doing something wrong (sparse bindings always go > >>> through vkQueueBindSparse). > >> User-space is allowed to create new bind queues at will, and they > >> execute independently save for range overlaps. > > I've limited panthor to just one bind-queue that's automatically > > created when the VM is created. I guess letting userspace create more > > than one queue is doable, but we'd still be serializing VM > > operations anyway and that complicates the whole thing when concurrent > > operations to the same VM region happen from different bind queues, so I > > figured it'd be simpler to expose just one queue. > > > >> And the overlapping granularity depends very much on the detail of the > >> range tracking. > >> We drafted this fenced range utility > >> > >> https://gitlab.freedesktop.org/drm/xe/kernel/-/merge_requests/353 > >> > >> That tracks active ranges that remove themselves when the attached fence > >> signals. Not sure if we ended up using it, though. A new binding would > >> scan this utility for dma-fences it needs to depend upon. > > Sounds like implicit deps on VM ranges :D. I'll have a look, thanks > > for the pointer! > > > >> Ranges in Xe > >> are actually page-table modification ranges, so can exceed the actual VA > >> range in some situations, but if you can build page-table structures > >> async the granularity indeed becomes better. > > The granularity in Mali is 4k, and we don't build the page table struct > > asynchronously, we just update the page table tree from the CPU, > > holding a VM lock to serialize such operations (that's done > > synchronously in the ::run_job() path, or from the ioctl in case of a > > sync-VM_BIND). > > OK, yeah we have something similar although we build the page-table tree > in the IOCTL and update entries using the GPU unless there are no > dependencies, We can't do that since we defer pgtable updates to the io-pgtable framework, which handles the pgtable tree update (we can't pass a pre-built version of the tree). What we did though, is extend the framework so we're in control of the page table allocations. In order to avoid allocations in the dma-signalling path, we pre-allocate page tables for the range we want to map (or unmap), and then pick from these pre-allocated pages when the iopgtable frameworks asks us to allocate a page table. Until now, we were provisioning for the worst case scenario (all levels of the page table tree are missing, except for the root level, which is allocated when the io-pgtable is instantiated). With per-range operation tracking, we could potentially avoid this over-provisioning by checking the queue of operations touching a specific range, and making sure unmaps don't teardown page tables if we now they're going to be needed later on (we just want to update PTEs in that case). > in which case we do it sync in the ioctl as well. > > The drawback here is that if one op adds a pagetable tree node near the > root (spanning say 1G) and the next op adds an entry to that node, the > granularity can become pretty large... I know nothing about the intel GPU MMU page table format, but I guess you're talking about adding one or more levels to the pgtable tree because some big physically contiguous mapping is split, which indeed might require allocating page tables and filling a lot of PTEs. This change of granularity indeed has a cost, and avoiding repeated changes would indeed be preferable, but it's not the end of the world for Panthor, where we only use 4k and 2M granules (only the last level is optional in our implementation).
