public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Daniel Vetter <daniel@ffwll.ch>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Fix list corruption in vma_unbind
Date: Thu, 29 Aug 2013 16:21:39 -0700	[thread overview]
Message-ID: <20130829232139.GA1022@bwidawsk.net> (raw)
In-Reply-To: <20130829211924.GL4726@nuc-i3427.alporthouse.com>

On Thu, Aug 29, 2013 at 10:19:24PM +0100, Chris Wilson wrote:
> On Thu, Aug 29, 2013 at 11:06:24PM +0200, Daniel Vetter wrote:
> > On Thu, Aug 29, 2013 at 07:57:38PM +0100, Chris Wilson wrote:
> > > On Thu, Aug 29, 2013 at 07:50:31PM +0200, Daniel Vetter wrote:
> > > > The saga around the breadcrumb vmas used by execbuf continues ...
> > > > 
> > > > This time around we've managed to unconditionally move the object to
> > > > the unbound list on the last vma unbind even though it might never
> > > > have been on either the bound or unbound list. Hilarity ensued.
> > > > 
> > > > Chris Wilson tracked this one down but compared to his patches I've
> > > > simply opted to completely separate the unbound case for not-yet bound
> > > > vmas. Otherwise we imo end up with semantically hard to parse checks
> > > > around the list_move_tail(global_list, ...).
> > > > 
> > > > This is exercised by the new swapping variants of
> > > > igt/tests/gem_evict_everything.
> > > > 
> > > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > > > Cc: Ben Widawsky <ben@bwidawsk.net>
> > > > Bugzilla: https://bugs.freedesktop.org/attachment.cgi?id=84818
> > > > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > 
> > > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> > 
> > Merged, but I've dropped the paragraph about the igt tests again - I just
> > can't hit the bug any more :( Also I've fixed the bugzilla link, it
> > pointed at an attachment instead of the bug.
> 
> It fixed the tests for me, just got a whole new trace when using GL.
> -Chris
> 
> -- 
> Chris Wilson, Intel Open Source Technology Centre

I'm not really sure why the assertion I added blew up :/
Tested-by: Ben Widawsky <ben@bwidawsk.net>

-- 
Ben Widawsky, Intel Open Source Technology Center

      reply	other threads:[~2013-08-29 23:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 17:50 [PATCH] drm/i915: Fix list corruption in vma_unbind Daniel Vetter
2013-08-29 18:57 ` Chris Wilson
2013-08-29 21:06   ` Daniel Vetter
2013-08-29 21:19     ` Chris Wilson
2013-08-29 23:21       ` Ben Widawsky [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130829232139.GA1022@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox