public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
	Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH] drm/i915: set ctx->initialized only after RCS
Date: Fri, 10 Jan 2014 08:18:25 +0100	[thread overview]
Message-ID: <20140110071825.GC4770@phenom.ffwll.local> (raw)
In-Reply-To: <20140109231725.GA4522@bwidawsk.net>

On Thu, Jan 09, 2014 at 03:17:25PM -0800, Ben Widawsky wrote:
> On Tue, Jan 07, 2014 at 10:47:18AM +0000, Chris Wilson wrote:
> > On Tue, Jan 07, 2014 at 08:10:33AM +0100, Daniel Vetter wrote:
> > > On Sat, Dec 28, 2013 at 01:31:49PM -0800, Ben Widawsky wrote:
> > > > The initialized flag is used to specify a context has been initialized
> > > > and it's context is safe to load, ie. the 3d state is setup properly.
> > > > With full PPGTT, we emit the address space loads during context switch
> > > > and this currently marks a context as initialized. With full PPGTT
> > > > patches, if a client first emits a batch to !RCS, then later, RCS, the
> > > > code will mistake the context as initialized and try to reload an
> > > > uninitialized context.
> > > > 
> > > > 1. context 1 blit // context initialized
> > > > 2. context 2 <X operation> // saves context 1 random state
> > > > 3. context 1 render // loads random state from step 2
> > > > 
> > > > It is really easy to hit this with a planned upcoming patch which makes
> > > > default context reuse possible.
> > > > 
> > > > NOTE: This should only effect full PPGTT branches, ie. current
> > > > drm-intel-nightly.
> > > > 
> > > > Thanks to Chris for helping me track this down.
> > > > 
> > > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > > > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > > 
> > > Do we have a testcase for this or a bug report?
> > 
> > Odd, since QA should have hit this...
> > -Chris
> 
> I was only able to hit it on one machine. The test case was 'startx.' I
> think getting it to fail is somewhat dependent upon how the backing
> pages for the context are initialized (at least, that is my theory).

Well I've hoped we'd understand the fallout a bit better, but meh. Patch
merged with the failure scenario in the commit message simplified as noted
by Chris.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-01-10  7:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28 21:31 [PATCH] drm/i915: set ctx->initialized only after RCS Ben Widawsky
2013-12-29  9:59 ` Chris Wilson
2013-12-30 21:34   ` Ben Widawsky
2013-12-31 11:26     ` Chris Wilson
2014-01-01 18:10       ` Ben Widawsky
2014-01-07  7:10 ` Daniel Vetter
2014-01-07 10:47   ` Chris Wilson
2014-01-09 23:17     ` Ben Widawsky
2014-01-10  7:18       ` Daniel Vetter [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=20140110071825.GC4770@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=ben@bwidawsk.net \
    --cc=benjamin.widawsky@intel.com \
    --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