Re: [Intel-gfx] [PATCH 16/40] drm/i915: Pull scheduling under standalone lock

2018-09-25 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-09-25 10:01:21) > > On 25/09/2018 09:19, Chris Wilson wrote: > > Quoting Tvrtko Ursulin (2018-09-24 12:19:39) > >> > >> On 19/09/2018 20:55, Chris Wilson wrote: > >>> diff --git a/drivers/gpu/drm/i915/i915_scheduler.c > >>> b/drivers/gpu/drm/i915/i915_scheduler.c > >>

Re: [Intel-gfx] [PATCH 16/40] drm/i915: Pull scheduling under standalone lock

2018-09-25 Thread Tvrtko Ursulin
On 25/09/2018 10:10, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-09-25 10:01:21) On 25/09/2018 09:19, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-09-24 12:19:39) On 19/09/2018 20:55, Chris Wilson wrote: diff --git a/drivers/gpu/drm/i915/i915_scheduler.c b/drivers/gpu/drm/i915/i9

Re: [Intel-gfx] [PATCH 16/40] drm/i915: Pull scheduling under standalone lock

2018-09-25 Thread Tvrtko Ursulin
On 25/09/2018 09:19, Chris Wilson wrote: Quoting Tvrtko Ursulin (2018-09-24 12:19:39) On 19/09/2018 20:55, Chris Wilson wrote: diff --git a/drivers/gpu/drm/i915/i915_scheduler.c b/drivers/gpu/drm/i915/i915_scheduler.c new file mode 100644 index ..910ac7089596 --- /dev/null +++ b/

Re: [Intel-gfx] [PATCH 16/40] drm/i915: Pull scheduling under standalone lock

2018-09-25 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-09-24 12:19:39) > > On 19/09/2018 20:55, Chris Wilson wrote: > > diff --git a/drivers/gpu/drm/i915/i915_scheduler.c > > b/drivers/gpu/drm/i915/i915_scheduler.c > > new file mode 100644 > > index ..910ac7089596 > > --- /dev/null > > +++ b/drivers/gpu/drm/i9

Re: [Intel-gfx] [PATCH 16/40] drm/i915: Pull scheduling under standalone lock

2018-09-24 Thread Tvrtko Ursulin
On 19/09/2018 20:55, Chris Wilson wrote: Currently, the backend scheduling code abuses struct_mutex into order to have a global lock to manipulate a temporary list (without widespread allocation) and to protect against list modifications. This is an extraneous coupling to struct_mutex and furthe

[Intel-gfx] [PATCH 16/40] drm/i915: Pull scheduling under standalone lock

2018-09-19 Thread Chris Wilson
Currently, the backend scheduling code abuses struct_mutex into order to have a global lock to manipulate a temporary list (without widespread allocation) and to protect against list modifications. This is an extraneous coupling to struct_mutex and further can not extend beyond the local device. P