iris: Update comment in iris_cache_flush_for_render

Update the comment to reflect the fact that iris no longer switches
between CCS_E and CCS_D.

Cc: 23.0 <mesa-stable>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21303>
(cherry picked from commit ad9c0b7a84)
This commit is contained in:
Nanley Chery 2023-02-13 16:45:02 -08:00 committed by Dylan Baker
parent 4a983470b8
commit 76e3530f45
2 changed files with 3 additions and 3 deletions

View file

@ -517,7 +517,7 @@
"description": "iris: Update comment in iris_cache_flush_for_render",
"nominated": true,
"nomination_type": 0,
"resolution": 0,
"resolution": 1,
"main_sha": null,
"because_sha": null
},

View file

@ -398,10 +398,10 @@ iris_cache_flush_for_render(struct iris_batch *batch,
* but with a different aux usage. If it has, flush the render cache so we
* ensure that it's only in there with one aux usage at a time.
*
* Even though it's not obvious, this can easily happen in practice.
* Even though it's not obvious, this could easily happen in practice.
* Suppose a client is blending on a surface with sRGB encode enabled on
* gfx9. This implies that you get AUX_USAGE_CCS_D at best. If the client
* then disables sRGB decode and continues blending we will flip on
* then disables sRGB decode and continues blending we could flip on
* AUX_USAGE_CCS_E without doing any sort of resolve in-between (this is
* perfectly valid since CCS_E is a subset of CCS_D). However, this means
* that we have fragments in-flight which are rendering with UNORM+CCS_E