Re: [Intel-gfx] [PATCH igt v3] Iterate over physical engines

2018-02-22 Thread Tvrtko Ursulin
On 22/02/2018 07:52, Chris Wilson wrote: We current have a single for_each_engine() iterator which we use to generate both a set of uABI engines and a set of physical engines. Determining what uABI ring-id corresponds to an actual HW engine is tricky, so pull that out to a library function and

[Intel-gfx] [PATCH igt v3] Iterate over physical engines

2018-02-21 Thread Chris Wilson
We current have a single for_each_engine() iterator which we use to generate both a set of uABI engines and a set of physical engines. Determining what uABI ring-id corresponds to an actual HW engine is tricky, so pull that out to a library function and introduce for_each_physical_engine() for