gallium: clarify reference counting for fence
Nowhere was it spelled out that the state tracker may expect the pipe driver to unref the old fence. Signed-off-by: Rob Clark <robclark@freedesktop.org> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Reviewed-by: Marek Olšák <marek.olsak@amd.com>
This commit is contained in:
parent
0a8af6361e
commit
f60354ee72
|
@ -361,8 +361,14 @@ struct pipe_context {
|
||||||
const void *clear_value,
|
const void *clear_value,
|
||||||
int clear_value_size);
|
int clear_value_size);
|
||||||
|
|
||||||
/** Flush draw commands
|
/**
|
||||||
|
* Flush draw commands
|
||||||
*
|
*
|
||||||
|
* NOTE: use screen->fence_reference() (or equivalent) to transfer
|
||||||
|
* new fence ref to **fence, to ensure that previous fence is unref'd
|
||||||
|
*
|
||||||
|
* \param fence if not NULL, an old fence to unref and transfer a
|
||||||
|
* new fence reference to
|
||||||
* \param flags bitfield of enum pipe_flush_flags values.
|
* \param flags bitfield of enum pipe_flush_flags values.
|
||||||
*/
|
*/
|
||||||
void (*flush)(struct pipe_context *pipe,
|
void (*flush)(struct pipe_context *pipe,
|
||||||
|
|
Loading…
Reference in New Issue