Am 25.06.20 um 17:10 schrieb Chris Wilson:
We have the DAG of fences, we can use that information to avoid adding
an implicit coupling between execution contexts.
No, we can't. And it sounds like you still have not understood the
underlying problem.
See this has nothing to do with the fences itself or their DAG.
When you depend on userspace to do another submission so your fence can
start processing you end up depending on whatever userspace does.
This in turn means when userspace calls a system call (or does page
fault) it is possible that this ends up in the reclaim code path.
And while we want to avoid it both Daniel and I already discussed this
multiple times and we agree it is still a must have to be able to do
fence waits in the reclaim code path.
So what happens is that you have a dependency between fence submission
-> userspace -> reclaim path -> fence submission. And that is a circle
dependency, no matter what your DAG looks like.
In other words this whole approach does not work, is a clear NAK and I
can only advise Dave to *not* merge it.
Regards,
Christian.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
