Re: [Intel-gfx] [PATCH] drm/i915: Mark up nested spinlocks

2018-05-14 Thread Chris Wilson
Quoting Chris Wilson (2018-05-14 11:43:44) > Quoting Chris Wilson (2018-05-12 09:49:57) > > When we process the outstanding requests upon banning a context, we need > > to acquire both the engine and the client's timeline, nesting the locks. > > This requires explicit markup as the two timelines ar

Re: [Intel-gfx] [PATCH] drm/i915: Mark up nested spinlocks

2018-05-14 Thread Chris Wilson
Quoting Chris Wilson (2018-05-12 09:49:57) > When we process the outstanding requests upon banning a context, we need > to acquire both the engine and the client's timeline, nesting the locks. > This requires explicit markup as the two timelines are now of the same > class, since commit a89d1f921c1

[Intel-gfx] [PATCH] drm/i915: Mark up nested spinlocks

2018-05-12 Thread Chris Wilson
When we process the outstanding requests upon banning a context, we need to acquire both the engine and the client's timeline, nesting the locks. This requires explicit markup as the two timelines are now of the same class, since commit a89d1f921c15 ("drm/i915: Split i915_gem_timeline into individu