Lines Matching refs:GPU

5 Broadcom's VideoCore IV GPU. It is notably used in the Raspberry Pi 0
16 GPU block from Linux.
76 For GPU hangs, if you can get a short apitrace that produces the
99     (GPU) Initialize the per-tile draw call lists to empty.
100     (GPU) Run all draw calls collecting vertex data
101     (GPU) For each tile covered by a draw call's primitive.
117 from memory, in favor of a cheap GPU-side ``memset()`` of the tile
155 * Increasing GPU memory Increase CMA pool size
192 * Step 2: CPU vs GPU
195 application, the CPU is busy in the GL driver, the GPU is waiting for
196 the CPU, or the CPU is waiting for the GPU. Ideally, you get to the
197 point where the CPU is waiting for the GPU infrequently but for a
198 significant amount of time (however long it takes the GPU to draw a
203 sysprof. If it's not very high, is the GPU staying busy? We don't have
206 means that the GPU is currently busy processing some rendering job.
210 If the CPU is totally busy and the GPU isn't terribly busy, there is
228 * perf for CPU waits on GPU
230 If the CPU is not very busy and the GPU is not very busy, then we're
247 * Debugging for GPU fully busy
294 is closely related to the vc4 GPU present in the Raspberry Pi.  They
302 the GPU.  The Mesa driver includes a backend (`vc4_simulator.c`) to
305 to the real GPU.