From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] drm/i915: Use LRI to update the semaphore
 registers
Date: Thu, 15 Nov 2012 09:14:48 -0800
Message-ID: <20121115091448.7d1c5782@bwidawsk.net>
References: <1352884515-10154-1-git-send-email-chris@chris-wilson.co.uk>
	<20121114110642.397ca341@bwidawsk.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from shiva.chad-versace.us (209-20-75-48.static.cloud-ips.com
	[209.20.75.48])
	by gabe.freedesktop.org (Postfix) with ESMTP id 9D35BA08A9
	for <intel-gfx@lists.freedesktop.org>;
	Thu, 15 Nov 2012 09:15:02 -0800 (PST)
In-Reply-To: <20121114110642.397ca341@bwidawsk.net>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org, Daniel J Blueman <daniel@quora.org>
List-Id: intel-gfx@lists.freedesktop.org

On Wed, 14 Nov 2012 11:06:42 -0800
Ben Widawsky <ben@bwidawsk.net> wrote:

> On Wed, 14 Nov 2012 09:15:14 +0000
> Chris Wilson <chris@chris-wilson.co.uk> wrote:
> 
> > The bspec was recently updated to remove the ability to update the
> > semaphore using the MI_SEMAPHORE_BOX command, the ability to wait upon
> > the semaphore value remained. Instead the advice is to update the
> > register using the MI_LOAD_REGISTER_IMM command. In cursory testing,
> > semaphores continue to function - the question is whether this fixes
> > some of the deadlocks where the semaphore registers contained stale
> > values?
> > 
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Daniel J Blueman <daniel@quora.org>
> Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
Tested-by: Ben Widawsky <ben@bwidawsk.net>
 
> > ---
> >  drivers/gpu/drm/i915/intel_ringbuffer.c |    7 ++-----
> >  1 file changed, 2 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index ee4abc5..dd2e7db 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -554,12 +554,9 @@ update_mboxes(struct intel_ring_buffer *ring,
> >  	    u32 seqno,
> >  	    u32 mmio_offset)
> >  {
> > -	intel_ring_emit(ring, MI_SEMAPHORE_MBOX |
> > -			      MI_SEMAPHORE_GLOBAL_GTT |
> > -			      MI_SEMAPHORE_REGISTER |
> > -			      MI_SEMAPHORE_UPDATE);
> > -	intel_ring_emit(ring, seqno);
> > +	intel_ring_emit(ring, MI_LOAD_REGISTER_IMM(1));
> >  	intel_ring_emit(ring, mmio_offset);
> > +	intel_ring_emit(ring, seqno);
> >  }
> >  
> >  /**
> 
> 
> 



-- 
Ben Widawsky, Intel Open Source Technology Center