I think you may have missed Lucas' reply to your v3:
https://lists.freedesktop.org/archives/intel-gfx/2022-June/300712.html
Also, here's the reply to v2 that he's referring to:
https://lists.freedesktop.org/archives/intel-gfx/2022-June/300646.html
I.e., he wants this to be called from a new 'tu
Ping?
On 11/07/2022 14:30, Lionel Landwerlin wrote:
Ping?
On 30/06/2022 11:35, Lionel Landwerlin wrote:
The recommended number of stackIDs for Ray Tracing subsystem is 512
rather than 2048 (default HW programming).
v2: Move the programming to dg2_ctx_gt_tuning_init() (Lucas)
v3: Move program
Ping?
On 30/06/2022 11:35, Lionel Landwerlin wrote:
The recommended number of stackIDs for Ray Tracing subsystem is 512
rather than 2048 (default HW programming).
v2: Move the programming to dg2_ctx_gt_tuning_init() (Lucas)
v3: Move programming to general_render_compute_wa_init() (Matt)
Signe
"Add performance tuning for RT_CTRL" would be more accurate as this is
handled as a workaround in the spec.
On Thu, Jun 30, 2022 at 11:35:08AM +0300, Lionel Landwerlin wrote:
The recommended number of stackIDs for Ray Tracing subsystem is 512
rather than 2048 (default HW programming).
v2: Move
The recommended number of stackIDs for Ray Tracing subsystem is 512
rather than 2048 (default HW programming).
v2: Move the programming to dg2_ctx_gt_tuning_init() (Lucas)
v3: Move programming to general_render_compute_wa_init() (Matt)
Signed-off-by: Lionel Landwerlin
---
drivers/gpu/drm/i915/
