diff options
author | Topi Pohjolainen <[email protected]> | 2016-04-22 11:25:18 +0300 |
---|---|---|
committer | Topi Pohjolainen <[email protected]> | 2016-04-23 07:09:39 +0300 |
commit | 65a5af6dd0550e93a5250582147689a1ddef9ffa (patch) | |
tree | 5732f1c9f80450ac4a9f111df14821e0779dbe87 /src/mesa/drivers/dri/i965/gen7_l3_state.c | |
parent | 0e850452d1af72ae2af3a77892483bd1564af481 (diff) |
i965: Introduce state flag for blorp
In the past, BLORP has clobbered all BRW_NEW_* state flags, to trigger
re-emission of the entire 3D pipeline on the next draw. However, there
are some packets BLORP simply leaves alone, so there's no need to
re-emit them. Trying to reduce the set of dirty bits flagged after
BLORP runs is tricky.
Instead, we introduce a BRW_NEW_BLORP flag. This should be set on any
atom which emits a packet that BLORP also emits. When BLORP runs, it
will flag BRW_NEW_BLORP, causing those packets to get re-emitted.
This also makes it easy to avoid re-emitting specific atoms - we can
simply drop the BRW_NEW_BLORP flag on those.
To start, we assume that all packets need to be re-emitted. This is the
safest approach and closest to the existing code's behavior. Many of
these are obviously not required, and can be dropped in subsequent
patches.
Signed-off-by: Topi Pohjolainen <[email protected]>
Signed-off-by: Kenneth Graunke <[email protected]>
Diffstat (limited to 'src/mesa/drivers/dri/i965/gen7_l3_state.c')
0 files changed, 0 insertions, 0 deletions