[Intel-gfx] [PATCH 4/6] drm/i915: Move timeline from GTT to ring

2018-04-24 Thread Chris Wilson
In the future, we want to move a request between engines. To achieve this, we first realise that we have two timelines in effect here. The first runs through the GTT is required for ordering vma access, which is tracked currently by engine. The second is implied by sequential execution of commands

Re: [Intel-gfx] [PATCH 4/6] drm/i915: Move timeline from GTT to ring

2018-04-23 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-04-23 11:44:19) > > On 23/04/2018 11:13, Chris Wilson wrote: > > diff --git a/drivers/gpu/drm/i915/i915_gem.c > > b/drivers/gpu/drm/i915/i915_gem.c > > index 0097a77fae8d..1635975dbc16 100644 > > --- a/drivers/gpu/drm/i915/i915_gem.c > > +++ b/drivers/gpu/drm/i915/i91

Re: [Intel-gfx] [PATCH 4/6] drm/i915: Move timeline from GTT to ring

2018-04-23 Thread Tvrtko Ursulin
On 23/04/2018 11:13, Chris Wilson wrote: In the future, we want to move a request between engines. To achieve this, we first realise that we have two timelines in effect here. The first runs through the GTT is required for ordering vma access, which is tracked currently by engine. The second is

[Intel-gfx] [PATCH 4/6] drm/i915: Move timeline from GTT to ring

2018-04-23 Thread Chris Wilson
In the future, we want to move a request between engines. To achieve this, we first realise that we have two timelines in effect here. The first runs through the GTT is required for ordering vma access, which is tracked currently by engine. The second is implied by sequential execution of commands