iris: Enable fast clears on other miplevels and layers than 0.
[mesa.git] / src / gallium / drivers / iris / iris_pipe_control.c
1 /*
2 * Copyright © 2017 Intel Corporation
3 *
4 * Permission is hereby granted, free of charge, to any person obtaining a
5 * copy of this software and associated documentation files (the "Software"),
6 * to deal in the Software without restriction, including without limitation
7 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
8 * and/or sell copies of the Software, and to permit persons to whom the
9 * Software is furnished to do so, subject to the following conditions:
10 *
11 * The above copyright notice and this permission notice shall be included
12 * in all copies or substantial portions of the Software.
13 *
14 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
15 * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
16 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
17 * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
18 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
19 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
20 * DEALINGS IN THE SOFTWARE.
21 */
22
23 /**
24 * @file iris_pipe_control.c
25 *
26 * PIPE_CONTROL is the main flushing and synchronization primitive on Intel
27 * GPUs. It can invalidate caches, stall until rendering reaches various
28 * stages of completion, write to memory, and other things. In a way, it's
29 * a swiss army knife command - it has all kinds of capabilities, but some
30 * significant limitations as well.
31 *
32 * Unfortunately, it's notoriously complicated and difficult to use. Many
33 * sub-commands can't be used together. Some are meant to be used at the
34 * top of the pipeline (invalidating caches before drawing), while some are
35 * meant to be used at the end (stalling or flushing after drawing).
36 *
37 * Also, there's a list of restrictions a mile long, which vary by generation.
38 * Do this before doing that, or suffer the consequences (usually a GPU hang).
39 *
40 * This file contains helpers for emitting them safely. You can simply call
41 * iris_emit_pipe_control_flush() with the desired operations (as logical
42 * PIPE_CONTROL_* bits), and it will take care of splitting it into multiple
43 * PIPE_CONTROL commands as necessary. The per-generation workarounds are
44 * applied in iris_emit_raw_pipe_control() in iris_state.c.
45 */
46
47 #include "iris_context.h"
48 #include "util/hash_table.h"
49 #include "util/set.h"
50
51 /**
52 * Emit a PIPE_CONTROL with various flushing flags.
53 *
54 * The caller is responsible for deciding what flags are appropriate for the
55 * given generation.
56 */
57 void
58 iris_emit_pipe_control_flush(struct iris_batch *batch,
59 const char *reason,
60 uint32_t flags)
61 {
62 if ((flags & PIPE_CONTROL_CACHE_FLUSH_BITS) &&
63 (flags & PIPE_CONTROL_CACHE_INVALIDATE_BITS)) {
64 /* A pipe control command with flush and invalidate bits set
65 * simultaneously is an inherently racy operation on Gen6+ if the
66 * contents of the flushed caches were intended to become visible from
67 * any of the invalidated caches. Split it in two PIPE_CONTROLs, the
68 * first one should stall the pipeline to make sure that the flushed R/W
69 * caches are coherent with memory once the specified R/O caches are
70 * invalidated. On pre-Gen6 hardware the (implicit) R/O cache
71 * invalidation seems to happen at the bottom of the pipeline together
72 * with any write cache flush, so this shouldn't be a concern. In order
73 * to ensure a full stall, we do an end-of-pipe sync.
74 */
75 iris_emit_end_of_pipe_sync(batch, reason,
76 flags & PIPE_CONTROL_CACHE_FLUSH_BITS);
77 flags &= ~(PIPE_CONTROL_CACHE_FLUSH_BITS | PIPE_CONTROL_CS_STALL);
78 }
79
80 batch->vtbl->emit_raw_pipe_control(batch, reason, flags, NULL, 0, 0);
81 }
82
83 /**
84 * Emit a PIPE_CONTROL that writes to a buffer object.
85 *
86 * \p flags should contain one of the following items:
87 * - PIPE_CONTROL_WRITE_IMMEDIATE
88 * - PIPE_CONTROL_WRITE_TIMESTAMP
89 * - PIPE_CONTROL_WRITE_DEPTH_COUNT
90 */
91 void
92 iris_emit_pipe_control_write(struct iris_batch *batch,
93 const char *reason, uint32_t flags,
94 struct iris_bo *bo, uint32_t offset,
95 uint64_t imm)
96 {
97 batch->vtbl->emit_raw_pipe_control(batch, reason, flags, bo, offset, imm);
98 }
99
100 /*
101 * From Sandybridge PRM, volume 2, "1.7.2 End-of-Pipe Synchronization":
102 *
103 * Write synchronization is a special case of end-of-pipe
104 * synchronization that requires that the render cache and/or depth
105 * related caches are flushed to memory, where the data will become
106 * globally visible. This type of synchronization is required prior to
107 * SW (CPU) actually reading the result data from memory, or initiating
108 * an operation that will use as a read surface (such as a texture
109 * surface) a previous render target and/or depth/stencil buffer
110 *
111 * From Haswell PRM, volume 2, part 1, "End-of-Pipe Synchronization":
112 *
113 * Exercising the write cache flush bits (Render Target Cache Flush
114 * Enable, Depth Cache Flush Enable, DC Flush) in PIPE_CONTROL only
115 * ensures the write caches are flushed and doesn't guarantee the data
116 * is globally visible.
117 *
118 * SW can track the completion of the end-of-pipe-synchronization by
119 * using "Notify Enable" and "PostSync Operation - Write Immediate
120 * Data" in the PIPE_CONTROL command.
121 */
122 void
123 iris_emit_end_of_pipe_sync(struct iris_batch *batch,
124 const char *reason, uint32_t flags)
125 {
126 /* From Sandybridge PRM, volume 2, "1.7.3.1 Writing a Value to Memory":
127 *
128 * "The most common action to perform upon reaching a synchronization
129 * point is to write a value out to memory. An immediate value
130 * (included with the synchronization command) may be written."
131 *
132 * From Broadwell PRM, volume 7, "End-of-Pipe Synchronization":
133 *
134 * "In case the data flushed out by the render engine is to be read
135 * back in to the render engine in coherent manner, then the render
136 * engine has to wait for the fence completion before accessing the
137 * flushed data. This can be achieved by following means on various
138 * products: PIPE_CONTROL command with CS Stall and the required
139 * write caches flushed with Post-Sync-Operation as Write Immediate
140 * Data.
141 *
142 * Example:
143 * - Workload-1 (3D/GPGPU/MEDIA)
144 * - PIPE_CONTROL (CS Stall, Post-Sync-Operation Write Immediate
145 * Data, Required Write Cache Flush bits set)
146 * - Workload-2 (Can use the data produce or output by Workload-1)
147 */
148 iris_emit_pipe_control_write(batch, reason,
149 flags | PIPE_CONTROL_CS_STALL |
150 PIPE_CONTROL_WRITE_IMMEDIATE,
151 batch->screen->workaround_bo, 0, 0);
152 }
153
154 static void
155 iris_texture_barrier(struct pipe_context *ctx, unsigned flags)
156 {
157 struct iris_context *ice = (void *) ctx;
158 struct iris_batch *render_batch = &ice->batches[IRIS_BATCH_RENDER];
159 struct iris_batch *compute_batch = &ice->batches[IRIS_BATCH_COMPUTE];
160
161 if (render_batch->contains_draw ||
162 render_batch->cache.render->entries ||
163 render_batch->cache.depth->entries) {
164 iris_batch_maybe_flush(render_batch, 48);
165 iris_emit_pipe_control_flush(render_batch,
166 "API: texture barrier (1/2)",
167 PIPE_CONTROL_DEPTH_CACHE_FLUSH |
168 PIPE_CONTROL_RENDER_TARGET_FLUSH |
169 PIPE_CONTROL_CS_STALL);
170 iris_emit_pipe_control_flush(render_batch,
171 "API: texture barrier (2/2)",
172 PIPE_CONTROL_TEXTURE_CACHE_INVALIDATE);
173 }
174
175 if (compute_batch->contains_draw) {
176 iris_batch_maybe_flush(compute_batch, 48);
177 iris_emit_pipe_control_flush(compute_batch,
178 "API: texture barrier (1/2)",
179 PIPE_CONTROL_CS_STALL);
180 iris_emit_pipe_control_flush(compute_batch,
181 "API: texture barrier (2/2)",
182 PIPE_CONTROL_TEXTURE_CACHE_INVALIDATE);
183 }
184 }
185
186 static void
187 iris_memory_barrier(struct pipe_context *ctx, unsigned flags)
188 {
189 struct iris_context *ice = (void *) ctx;
190 unsigned bits = PIPE_CONTROL_DATA_CACHE_FLUSH | PIPE_CONTROL_CS_STALL;
191
192 if (flags & (PIPE_BARRIER_VERTEX_BUFFER |
193 PIPE_BARRIER_INDEX_BUFFER |
194 PIPE_BARRIER_INDIRECT_BUFFER)) {
195 bits |= PIPE_CONTROL_VF_CACHE_INVALIDATE;
196 }
197
198 if (flags & PIPE_BARRIER_CONSTANT_BUFFER) {
199 bits |= PIPE_CONTROL_TEXTURE_CACHE_INVALIDATE |
200 PIPE_CONTROL_CONST_CACHE_INVALIDATE;
201 }
202
203 if (flags & (PIPE_BARRIER_TEXTURE | PIPE_BARRIER_FRAMEBUFFER)) {
204 bits |= PIPE_CONTROL_TEXTURE_CACHE_INVALIDATE |
205 PIPE_CONTROL_RENDER_TARGET_FLUSH;
206 }
207
208 for (int i = 0; i < IRIS_BATCH_COUNT; i++) {
209 if (ice->batches[i].contains_draw ||
210 ice->batches[i].cache.render->entries) {
211 iris_batch_maybe_flush(&ice->batches[i], 24);
212 iris_emit_pipe_control_flush(&ice->batches[i], "API: memory barrier",
213 bits);
214 }
215 }
216 }
217
218 void
219 iris_init_flush_functions(struct pipe_context *ctx)
220 {
221 ctx->memory_barrier = iris_memory_barrier;
222 ctx->texture_barrier = iris_texture_barrier;
223 }