[Intel-gfx] [PATCH 5/6] drm/i915: Split i915_gem_timeline into individual timelines

We need to move to a more flexible timeline that doesn't assume one fence context per engine, and so allow for a single timeline to be used across a combination of engines. This means that preallocating a fence context per engine is now a hindrance, and so we want to introduce the singular timeline

Re: [Intel-gfx] [PATCH 5/6] drm/i915: Split i915_gem_timeline into individual timelines

Quoting Tvrtko Ursulin (2018-04-23 13:33:04) > > On 23/04/2018 11:13, Chris Wilson wrote: > > We need to move to a more flexible timeline that doesn't assume one > > fence context per engine, and so allow for a single timeline to be used > > across a combination of engines. This means that preallo

Re: [Intel-gfx] [PATCH 5/6] drm/i915: Split i915_gem_timeline into individual timelines

On 23/04/2018 11:13, Chris Wilson wrote: We need to move to a more flexible timeline that doesn't assume one fence context per engine, and so allow for a single timeline to be used across a combination of engines. This means that preallocating a fence context per engine is now a hindrance, and s

[Intel-gfx] [PATCH 5/6] drm/i915: Split i915_gem_timeline into individual timelines

We need to move to a more flexible timeline that doesn't assume one fence context per engine, and so allow for a single timeline to be used across a combination of engines. This means that preallocating a fence context per engine is now a hindrance, and so we want to introduce the singular timeline