Re: [Intel-gfx] [PATCH 7/7] drm/i915: Engine queues query

2018-04-06 Thread Chris Wilson
Quoting Lionel Landwerlin (2018-04-05 14:05:52) > On 05/04/18 13:39, Tvrtko Ursulin wrote: > > + > > + /** Number of requests with unresolved fences and dependencies. */ > > + __u32 queued; > > + > > + /** Number of ready requests waiting on a slot on GPU. */ > > + __u32 runnable;

Re: [Intel-gfx] [PATCH 7/7] drm/i915: Engine queues query

2018-04-05 Thread Lionel Landwerlin
Looks fine to me, I would just add some comments on the uAPI. Otherwise : Reviewed-by: Lionel Landwerlin On 05/04/18 13:39, Tvrtko Ursulin wrote: From: Tvrtko Ursulin As well as exposing active requests on engines via PMU, we can

Re: [Intel-gfx] [PATCH 7/7] drm/i915: Engine queues query

2018-03-31 Thread Chris Wilson
Quoting Lionel Landwerlin (2018-03-31 02:04:26) > On 19/03/18 18:16, Tvrtko Ursulin wrote: > > From: Tvrtko Ursulin > > > > As well as exposing active requests on engines via PMU, we can also export > > the current raw values (as tracked by i915 command submission) via a

Re: [Intel-gfx] [PATCH 7/7] drm/i915: Engine queues query

2018-03-30 Thread Lionel Landwerlin
On 19/03/18 18:16, Tvrtko Ursulin wrote: From: Tvrtko Ursulin As well as exposing active requests on engines via PMU, we can also export the current raw values (as tracked by i915 command submission) via a dedicated query. This is to satisfy customers who have