[Intel-gfx] [PATCH v5 3/4] drm/i915/bdw: Pin the context backing objects to GGTT on-demand

[Daniel Vetter]

On Tue, Nov 18, 2014 at 12:10:51PM +0530, Deepak S wrote:
> On Thursday 13 November 2014 03:58 PM, Thomas Daniel wrote:
> >diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
> >index 906b985..f7fa0f7 100644
> >--- a/drivers/gpu/drm/i915/intel_lrc.c
> >+++ b/drivers/gpu/drm/i915/intel_lrc.c
> >@@ -139,8 +139,6 @@
> >  #define GEN8_LR_CONTEXT_RENDER_SIZE (20 * PAGE_SIZE)
> >  #define GEN8_LR_CONTEXT_OTHER_SIZE (2 * PAGE_SIZE)
> >-#define GEN8_LR_CONTEXT_ALIGN 4096
> >-
> >  #define RING_EXECLIST_QFULL		(1 << 0x2)
> >  #define RING_EXECLIST1_VALID		(1 << 0x3)
> >  #define RING_EXECLIST0_VALID		(1 << 0x4)
> >@@ -801,9 +799,40 @@ void intel_logical_ring_advance_and_submit(struct intel_ringbuffer *ringbuf)
> >  	execlists_context_queue(ring, ctx, ringbuf->tail);
> >  }
> >+static int intel_lr_context_pin(struct intel_engine_cs *ring,
> >+		struct intel_context *ctx)
> >+{
> >+	struct drm_i915_gem_object *ctx_obj = ctx->engine[ring->id].state;
> >+	int ret = 0;
> >+
> >+	WARN_ON(!mutex_is_locked(&ring->dev->struct_mutex));
> 
> With pin specific mutex from previous patch set removed.

Pardon my ignorance but I'm completely lost on this review comment here.
Deepak, can you please elaborate what kind of lock on which exact version
of the previous patch you mean? I didn't find any locking at all in the
preceeding patch here ...

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch