From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH 0/6] ring seqno wrap handling
Date: Tue, 4 Dec 2012 23:03:20 +0100
Message-ID: <20121204220320.GG11556@phenom.ffwll.local>
References: <1354626725-8521-1-git-send-email-mika.kuoppala@intel.com>
	<6c3329$7g2496@orsmga002.jf.intel.com>
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 mail-ee0-f49.google.com (mail-ee0-f49.google.com [74.125.83.49])
	by gabe.freedesktop.org (Postfix) with ESMTP id 19003E6066
	for <intel-gfx@lists.freedesktop.org>;
	Tue,  4 Dec 2012 14:01:53 -0800 (PST)
Received: by mail-ee0-f49.google.com with SMTP id c4so2577686eek.36
	for <intel-gfx@lists.freedesktop.org>;
	Tue, 04 Dec 2012 14:01:53 -0800 (PST)
Content-Disposition: inline
In-Reply-To: <6c3329$7g2496@orsmga002.jf.intel.com>
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: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

On Tue, Dec 04, 2012 at 02:05:42PM +0000, Chris Wilson wrote:
> On Tue,  4 Dec 2012 15:11:59 +0200, Mika Kuoppala <mika.kuoppala@linux.intel.com> wrote:
> > Hi,
> > 
> > As Ben suggested, explicitly syncing across wrap boundary
> > revealed yet another set of issues that gem_stress didn't find.
> > 
> > So here is a patchset which addresses the syncing problems
> > across wrap boundary. Chris helped me to carve out seqno handling
> > ugliness from my initial attempts to handle the ring wrapping.
> > 
> > As I can't break this anymore, i added 6/6.
> > --Mika
> > 
> > Mika Kuoppala (6):
> >   drm/i915: Fix debugfs seqno info print to use uint
> >   drm/i915: Don't emit semaphore wait if wrap happened
> >   drm/i915: Split intel_ring_begin
> >   drm/i915: Add intel_ring_handle_seqno wrap
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> >   drm/i915: Add debugfs entry to read/write next_seqno
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>

Merged them all, thanks for patches&review.
> 
> >   drm/i915: Set initial seqno value close to wrap boundary
> *washes hands*

I'm feeling stupid/lucky/bold/whatever, also merged.

/me hides

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