Re: [Intel-gfx] [PATCH] drm/i915: Add a tracepoint for using a semaphore

On Wed, Sep 25, 2013 at 02:29:34PM +0300, Ville Syrjälä wrote: > On Wed, Sep 25, 2013 at 11:43:28AM +0100, Chris Wilson wrote: > > So that we can find the callers who introduce a ring stall. A single > > ring stall is not too unwelcome, the right issue becomes when they start > > to interlock and p

Re: [Intel-gfx] [PATCH] drm/i915: Add a tracepoint for using a semaphore

On Wed, Sep 25, 2013 at 11:43:28AM +0100, Chris Wilson wrote: > So that we can find the callers who introduce a ring stall. A single > ring stall is not too unwelcome, the right issue becomes when they start > to interlock and prevent any concurrent work. That, however, is a little > tricker to det

[Intel-gfx] [PATCH] drm/i915: Add a tracepoint for using a semaphore

So that we can find the callers who introduce a ring stall. A single ring stall is not too unwelcome, the right issue becomes when they start to interlock and prevent any concurrent work. That, however, is a little tricker to detect with a mere tracepoint! v2: Rebrand it as a ring event, rather th

[Intel-gfx] [PATCH] drm/i915: Add a tracepoint for using a semaphore

So that we can find the callers who introduce a ring stall. A single ring stall is not too unwelcome, the right issue becomes when they start to interlock and prevent any concurrent work. That, however, is a little tricker to detect with a mere tracepoint! v2: Rebrand it as a ring event, rather th

Re: [Intel-gfx] [PATCH] drm/i915: Add a tracepoint for using a semaphore

On Mon, Aug 26, 2013 at 04:20:06PM +0300, Ville Syrjälä wrote: > On Mon, Aug 26, 2013 at 01:46:21PM +0100, Chris Wilson wrote: > > So that we can find the callers who introduce a ring stall. A single > > ring stall is not too unwelcome, the right issue becomes when they start > > to interlock and p

Re: [Intel-gfx] [PATCH] drm/i915: Add a tracepoint for using a semaphore

On Mon, Aug 26, 2013 at 01:46:21PM +0100, Chris Wilson wrote: > So that we can find the callers who introduce a ring stall. A single > ring stall is not too unwelcome, the right issue becomes when they start > to interlock and prevent any concurrent work. That, however, is a little > tricker to det

[Intel-gfx] [PATCH] drm/i915: Add a tracepoint for using a semaphore

So that we can find the callers who introduce a ring stall. A single ring stall is not too unwelcome, the right issue becomes when they start to interlock and prevent any concurrent work. That, however, is a little tricker to detect with a mere tracepoint! Signed-off-by: Chris Wilson --- drivers