Hi, > > > I am still catching up, but IIUC, indeed I don't think the host needs > > > to depend on fence_id. We should be able to repurpose fence_id. > > > > I'd rather ignore it altogether for FENCE_V2 (or whatever we call the > > feature flag). > > That's fine when one assumes each virtqueue has one host GPU timeline. > But when there are multiple (e.g., multiplexing multiple contexts over > one virtqueue, or multiple VkQueues), fence_id can be repurposed as > the host timeline id. Why do you need an id for that? You can simply keep track of the submit_3d commands instead. cheers, Gerd _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
