On Mon, May 18, 2015 at 10:30:06AM +0200, Daniel Vetter wrote:
On Fri, May 15, 2015 at 12:09:00PM +0100, Tvrtko Ursulin wrote:
Hi,
On 05/15/2015 11:42 AM, Chris Wilson wrote:
Mika encountered one pathological scenario under X where acquiring all
the mm locks (required to insert a
On Fri, May 15, 2015 at 12:09:00PM +0100, Tvrtko Ursulin wrote:
Hi,
On 05/15/2015 11:42 AM, Chris Wilson wrote:
Mika encountered one pathological scenario under X where acquiring all
the mm locks (required to insert a mmu notifier) was very slow, so slow
that by the time we tried to lock
On Mon, May 18, 2015 at 10:30:06AM +0200, Daniel Vetter wrote:
On Fri, May 15, 2015 at 12:09:00PM +0100, Tvrtko Ursulin wrote:
Hi,
On 05/15/2015 11:42 AM, Chris Wilson wrote:
Mika encountered one pathological scenario under X where acquiring all
the mm locks (required to insert a
On Mon, May 18, 2015 at 06:10:07PM +0100, Damien Lespiau wrote:
On Mon, May 18, 2015 at 10:30:06AM +0200, Daniel Vetter wrote:
On Fri, May 15, 2015 at 12:09:00PM +0100, Tvrtko Ursulin wrote:
Hi,
On 05/15/2015 11:42 AM, Chris Wilson wrote:
Mika encountered one pathological
Mika encountered one pathological scenario under X where acquiring all
the mm locks (required to insert a mmu notifier) was very slow, so slow
that by the time we tried to lock the struct_mutex with the usual call
to i915_mutex_lock_interruptible(), X's signal timer had fired causing
us to restart
Hi,
On 05/15/2015 11:42 AM, Chris Wilson wrote:
Mika encountered one pathological scenario under X where acquiring all
the mm locks (required to insert a mmu notifier) was very slow, so slow
that by the time we tried to lock the struct_mutex with the usual call
to
