[PATCH v9] tests/intel/xe_exec_capture: Add xe_exec_capture test

[Dong, Zhanjun]

On 2024-12-12 2:54 p.m., Teres Alexis, Alan Previn wrote:
> 
> Zhanjun, per offline chats with Kamil looks like we need to expand the
> igt_fixture sections before and after the igt_subtest section and
> save the per-engine-timeouts in the initial fixture and restore
> the per-engine-timeouts in the later fixture because the fixture
> section is not bypassed during an assert. That's what i understood.
> That said, we will need another rev of this.

Good point! the per-engine-timeouts should be restored to original value 
no matter of assert being triggered or not.
Although the save/restore for single vs multiple GPU might be different, 
I will take care of it in next rev.

Regards,
Zhanjun Dong
> 
> On Wed, 2024-12-11 at 14:08 -0800, Teres Alexis, Alan Previn wrote:
>> Just re-RB-ing after the recent addition for the change to set engine execution time manually before running the tests
>> on each engine in order to limit the execution time of this test:
>>
>> Reviewed-by: Alan Previn <alan.previn.teres.alexis at intel.com>
>>
>>
>> On Fri, 2024-12-06 at 14:59 -0800, Dong, Zhanjun wrote:
>>> Submit cmds to the GPU that result in a GuC engine reset and check that
>>> devcoredump register dump is generated, by the GuC, and includes the
>>> full register range.
>>>
>>> Signed-off-by: Zhanjun Dong <zhanjun.dong at intel.com>
>>> Cc: Alan Previn <alan.previn.teres.alexis at intel.com>
>>> Cc: Kamil Konieczny <kamil.konieczny at linux.intel.com>
>>> ---
>>> Changes from prior revs:
>>>   v9:-  Reduced job timeout to 2 seconds to speedup test
>>>         Add info print to show test is running on single/multiple GPU
>>>   v8:-  Move change list below ---
>>..