Re: [Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-23 Thread ch...@chris-wilson.co.uk
On Thu, Sep 22, 2016 at 04:05:51PM -0300, Paulo Zanoni wrote: > Em Qua, 2016-09-14 às 09:40 +0100, ch...@chris-wilson.co.uk escreveu: > > On Tue, Sep 13, 2016 at 03:21:48PM +0300, Mika Kuoppala wrote: > > > > > > Mika Kuoppala writes: > > > > > > > > "Zanoni,

Re: [Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-22 Thread Paulo Zanoni
Em Qua, 2016-09-14 às 09:40 +0100, ch...@chris-wilson.co.uk escreveu: > On Tue, Sep 13, 2016 at 03:21:48PM +0300, Mika Kuoppala wrote: > > > > Mika Kuoppala writes: > > > > > > "Zanoni, Paulo R" writes: > > > > > > > > > > > > > > +#if

Re: [Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-14 Thread ch...@chris-wilson.co.uk
On Tue, Sep 13, 2016 at 03:21:48PM +0300, Mika Kuoppala wrote: > Mika Kuoppala writes: > > "Zanoni, Paulo R" writes: > >>> +#if IS_ENABLED(CONFIG_LOCKDEP) > >>> + GEM_BUG_ON(!!lockdep_is_held(>i915->drm.struct_mutex) > >>> != > >>> +

Re: [Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-13 Thread Mika Kuoppala
Mika Kuoppala writes: > "Zanoni, Paulo R" writes: > >> Hi >> >> Em Sex, 2016-09-09 às 14:11 +0100, Chris Wilson escreveu: >>> In the next patch we want to handle reset directly by a locked waiter >>> in >>> order to avoid issues with

Re: [Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-13 Thread Mika Kuoppala
"Zanoni, Paulo R" writes: > Hi > > Em Sex, 2016-09-09 às 14:11 +0100, Chris Wilson escreveu: >> In the next patch we want to handle reset directly by a locked waiter >> in >> order to avoid issues with returning before the reset is handled. To >> handle the reset, we

Re: [Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-12 Thread Zanoni, Paulo R
Hi Em Sex, 2016-09-09 às 14:11 +0100, Chris Wilson escreveu: > In the next patch we want to handle reset directly by a locked waiter > in > order to avoid issues with returning before the reset is handled. To > handle the reset, we must first know whether we hold the > struct_mutex. > If we do

[Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-09 Thread Chris Wilson
In the next patch we want to handle reset directly by a locked waiter in order to avoid issues with returning before the reset is handled. To handle the reset, we must first know whether we hold the struct_mutex. If we do not hold the struct_mtuex we can not perform the reset, but we do not block

[Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-09 Thread Chris Wilson
In the next patch we want to handle reset directly by a locked waiter in order to avoid issues with returning before the reset is handled. To handle the reset, we must first know whether we hold the struct_mutex. If we do not hold the struct_mtuex we can not perform the reset, but we do not block

[Intel-gfx] [CI 10/21] drm/i915: Mark up all locked waiters

2016-09-09 Thread Chris Wilson
In the next patch we want to handle reset directly by a locked waiter in order to avoid issues with returning before the reset is handled. To handle the reset, we must first know whether we hold the struct_mutex. If we do not hold the struct_mtuex we can not perform the reset, but we do not block