Re: [Intel-gfx] [PATCH] drm/i915/guc: Decouple GuC engine id from ring id

2016-01-23 Thread Yu Dai
On 01/23/2016 10:25 AM, Chris Wilson wrote: On Fri, Jan 22, 2016 at 03:06:28PM -0800, yu@intel.com wrote: > From: Alex Dai > > Previously GuC uses ring id as engine id because of same definition. > But this is not true since this commit: > > commit de1add360522c876c25ef2ab1c94bdb509ab

Re: [Intel-gfx] [PATCH] drm/i915/guc: Decouple GuC engine id from ring id

2016-01-23 Thread Chris Wilson
On Fri, Jan 22, 2016 at 03:06:28PM -0800, yu@intel.com wrote: > From: Alex Dai > > Previously GuC uses ring id as engine id because of same definition. > But this is not true since this commit: > > commit de1add360522c876c25ef2ab1c94bdb509ab > Author: Tvrtko Ursulin > Date: Fri Jan 15

[Intel-gfx] [PATCH] drm/i915/guc: Decouple GuC engine id from ring id

2016-01-22 Thread yu . dai
From: Alex Dai Previously GuC uses ring id as engine id because of same definition. But this is not true since this commit: commit de1add360522c876c25ef2ab1c94bdb509ab Author: Tvrtko Ursulin Date: Fri Jan 15 15:12:50 2016 + drm/i915: Decouple execbuf uAPI from internal implementa