Displaying 3 results from an estimated 3 matches for "vksemaphor".
Did you mean:
vksemaphore
2018 Jan 12
2
[PATCH 0/3] drm/tegra: Add support for fence FDs
On Fri, Jan 12, 2018 at 10:40:16AM +0000, Chris Wilson wrote:
> Quoting Thierry Reding (2018-01-11 22:22:46)
> > From: Thierry Reding <treding at nvidia.com>
> >
> > This set of patches adds support for fences to Tegra DRM and complements
> > the fence FD support for Nouveau. Technically this isn't necessary for a
> > fence-based synchronization loop
2018 Jan 12
1
[PATCH 0/3] drm/tegra: Add support for fence FDs
...?
>
> Probably not, but if you don't need to force userspace to choose, they
> will come up with a situation where it is useful. Though one thing to
> consider with the drm_syncobj is that you will want to handle an array
> of in/out fences, as userspace will pass in an array of VkSemaphore (or
> whatever) rather than compute a singular dma_fence_array by merging.
It's fairly unlikely that Tegra DRM will ever need to be able to deal
with Vulkan (I'm not sure if the pre-Tegra124 GPU is capable of it). But
you're right, might be a good idea to plan for this anyway since...
2018 Jan 12
0
[PATCH 0/3] drm/tegra: Add support for fence FDs
...ult of the job submission?
Probably not, but if you don't need to force userspace to choose, they
will come up with a situation where it is useful. Though one thing to
consider with the drm_syncobj is that you will want to handle an array
of in/out fences, as userspace will pass in an array of VkSemaphore (or
whatever) rather than compute a singular dma_fence_array by merging.
> For the above it would suffice to add two additional flags:
>
> #define DRM_TEGRA_SUBMIT_WAIT_SYNCOBJ (1 << 2)
> #define DRM_TEGRA_SUBMIT_EMIT_SYNCOBJ (1 << 3)
>
> which wou...