From c40153ec8662e41c56f889e9a9a379d6758ee44c Mon Sep 17 00:00:00 2001 From: Mateusz Jablonski Date: Mon, 17 Jan 2022 18:25:23 +0000 Subject: [PATCH] Clarify logic of walk order values for Xe Hp and later Related-To: NEO-6466 Signed-off-by: Mateusz Jablonski --- .../command_encoder_xehp_and_later.inl | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/shared/source/command_container/command_encoder_xehp_and_later.inl b/shared/source/command_container/command_encoder_xehp_and_later.inl index 609c4ed70d..0a7de0e3e7 100644 --- a/shared/source/command_container/command_encoder_xehp_and_later.inl +++ b/shared/source/command_container/command_encoder_xehp_and_later.inl @@ -329,12 +329,15 @@ bool EncodeDispatchKernel::isRuntimeLocalIdsGenerationRequired(uint32_t //make sure table below matches Hardware Spec constexpr uint32_t walkOrderPossibilties = 6u; - constexpr uint8_t possibleWalkOrders[walkOrderPossibilties][3] = {{0, 1, 2}, - {0, 2, 1}, - {1, 0, 2}, - {2, 0, 1}, - {1, 2, 0}, - {2, 1, 0}}; + constexpr uint8_t X = 0; + constexpr uint8_t Y = 1; + constexpr uint8_t Z = 2; + constexpr uint8_t possibleWalkOrders[walkOrderPossibilties][3] = {{X, Y, Z}, // 0 1 2 + {X, Z, Y}, // 0 2 1 + {Y, X, Z}, // 1 0 2 + {Z, X, Y}, // 1 2 0 + {Y, Z, X}, // 2 0 1 + {Z, Y, X}}; // 2 1 0 //check if we need to follow kernel requirements if (requireInputWalkOrder) {