diff options
author | Marek Olšák <[email protected]> | 2016-08-06 16:41:42 +0200 |
---|---|---|
committer | Marek Olšák <[email protected]> | 2016-08-10 01:11:10 +0200 |
commit | 54272e18a682c8b82d4a86b2c07b51c303d8cead (patch) | |
tree | c9c0ac7ad2fb4144ebeb9c7851eaa19a8103973c /src/gallium/docs | |
parent | c6043e7d54fc48771856a50235f9141b711151f3 (diff) |
gallium: add a pipe_context parameter to fence_finish
required by glClientWaitSync (GL 4.5 Core spec) that can optionally flush
the context
Reviewed-by: Rob Clark <[email protected]>
Reviewed-by: Nicolai Hähnle <[email protected]>
Diffstat (limited to 'src/gallium/docs')
-rw-r--r-- | src/gallium/docs/source/context.rst | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/src/gallium/docs/source/context.rst b/src/gallium/docs/source/context.rst index 7fddabffeb4..1b045fa6ec0 100644 --- a/src/gallium/docs/source/context.rst +++ b/src/gallium/docs/source/context.rst @@ -467,12 +467,10 @@ Flushing PIPE_FLUSH_END_OF_FRAME: Whether the flush marks the end of frame. PIPE_FLUSH_DEFERRED: It is not required to flush right away, but it is required -to return a valid fence. The behavior of fence_finish or any other call isn't -changed. The only side effect can be that fence_finish will wait a little -longer. No guidance is given as to how drivers should implement fence_finish -with deferred flushes. If some drivers can't do deferred flushes safely, they -should just ignore the flag. - +to return a valid fence. If fence_finish is called with the returned fence +and the context is still unflushed, and the ctx parameter of fence_finish is +equal to the context where the fence was created, fence_finish will flush +the context. ``flush_resource`` |