anv: always use workaround_address, not workaround_bo

The workaround BO has some debug information at the beginning. The
workaround address is placed after that.

Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: mesa-stable
Reviewed-by: Ivan Briano <ivan.briano@intel.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30844>
This commit is contained in:
Lionel Landwerlin
2024-08-26 09:42:21 +03:00
committed by Marge Bot
parent 9b98cebe9a
commit d8ec8acede
+2 -8
View File
@@ -224,10 +224,7 @@ get_push_range_address(struct anv_cmd_buffer *cmd_buffer,
* bytes should be all zeros.
*/
assert(range->length * 32 <= 2048);
return (struct anv_address) {
.bo = cmd_buffer->device->workaround_bo,
.offset = 1024,
};
return cmd_buffer->device->workaround_address;
}
}
}
@@ -387,10 +384,7 @@ emit_null_push_constant_tbimr_workaround(struct anv_cmd_buffer *cmd_buffer)
* XXX - Use workaround infrastructure and final workaround
* when provided by hardware team.
*/
const struct anv_address null_addr = {
.bo = cmd_buffer->device->workaround_bo,
.offset = 1024,
};
const struct anv_address null_addr = cmd_buffer->device->workaround_address;
uint32_t *dw = anv_batch_emitn(
&cmd_buffer->batch, 4,
GENX(3DSTATE_CONSTANT_ALL),