diff options
| author | Jason Ekstrand <[email protected]> | 2016-05-20 11:49:12 -0700 |
|---|---|---|
| committer | Jason Ekstrand <[email protected]> | 2016-05-27 15:18:09 -0700 |
| commit | 3a83c176eab8c513eb723554a240af1a7308d701 (patch) | |
| tree | c24fac04d0ddcc91436f38423c2509401c54804a /src/intel/vulkan/gen8_cmd_buffer.c | |
| parent | 7120c75ec3046b48610f7423dff2b67e60f34be5 (diff) | |
anv/cmd_buffer: Only emit PIPE_CONTROL on-demand
This is in contrast to emitting it directly in vkCmdPipelineBarrier. This
has a couple of advantages. First, it means that no matter how many
vkCmdPipelineBarrier calls the application strings together it gets one or
two PIPE_CONTROLs. Second, it allow us to better track when we need to do
stalls because we can flag when a flush has happened and we need a stall.
Signed-off-by: Jason Ekstrand <[email protected]>
Reviewed-by: Jordan Justen <[email protected]>
Diffstat (limited to 'src/intel/vulkan/gen8_cmd_buffer.c')
| -rw-r--r-- | src/intel/vulkan/gen8_cmd_buffer.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/intel/vulkan/gen8_cmd_buffer.c b/src/intel/vulkan/gen8_cmd_buffer.c index 065cf9e7638..547fedd1eab 100644 --- a/src/intel/vulkan/gen8_cmd_buffer.c +++ b/src/intel/vulkan/gen8_cmd_buffer.c @@ -391,6 +391,8 @@ genX(cmd_buffer_flush_compute_state)(struct anv_cmd_buffer *cmd_buffer) } cmd_buffer->state.compute_dirty = 0; + + genX(cmd_buffer_apply_pipe_flushes)(cmd_buffer); } void genX(CmdSetEvent)( |