public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: "Mateo Lozano, Oscar" <oscar.mateo@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>, "miku@iki.fi" <miku@iki.fi>,
	"ben@bwidawsk.net" <ben@bwidawsk.net>,
	"kristen@linux.intel.com" <kristen@linux.intel.com>
Subject: Re: [PATCH v3 1/2] drm/i915: add render state initialization
Date: Wed, 14 May 2014 12:13:58 +0100	[thread overview]
Message-ID: <20140514111358.GC3022@strange.amr.corp.intel.com> (raw)
In-Reply-To: <92648605EABDA246B775AAB04C95A7A3012EE2FC@IRSMSX103.ger.corp.intel.com>

On Wed, May 14, 2014 at 10:24:53AM +0000, Mateo Lozano, Oscar wrote:
> Hi Mika,
> 
> > -----Original Message-----
> > From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf Of
> > Mika Kuoppala
> > Sent: Tuesday, May 06, 2014 3:30 PM
> > To: intel-gfx@lists.freedesktop.org
> > Cc: ben@bwidawsk.net; miku@iki.fi; kristen@linux.intel.com
> > Subject: [Intel-gfx] [PATCH v3 1/2] drm/i915: add render state initialization
> > 
> > HW guys say that it is not a cool idea to let device go into rc6 without proper 3d
> > pipeline state.
> > 
> > For each new uninitialized context, generate a valid null render state to be run
> > on context creation.
> 
> In Android, we have been seeing a problem in BDW D0 stepping (C0 is
> fine), in which actual rendering does not happen, even though
> everything seems to be healthy. The only "tell" seems to be that the
> pixel shader invocation count does not go up.  I wouldn´t dare say I
> understand why this fixes our problem, but it clearly does, so feel
> free to add:
> 
> Tested-by: Oscar Mateo <oscar.mateo@intel.com>

Stating the obvious here, mainly for my own understanding :)

FWIW, that looks like the userspace driver you are using actually
relying on the kernel setting up a golden state and missing "one bit" or
one packet. For instance it could be that it's missing a
3DSTATE_WM_HZ_OP command (that's the last fix Ken did in the gen8 render
copy state).

Out of sheer luck (or almost :) we happen to have this working.

So that's another kind of papering over than the one "needed" for rc6.

It seems to potentially be a useful service the kernel is providing to
user space apps though, trying to setup a sane state so user space
batches don't hang the GPU if they are missing one command. Of course
hangs can still happen if the batches themselves have bugs.

How to be sure that's the correct golden state is another interesting
question we need to answer.

-- 
Damien

  reply	other threads:[~2014-05-14 11:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 13:26 [PATCH v2 0/2] render state initialization (bdw rc6) Mika Kuoppala
2014-05-06 13:26 ` [PATCH v2 1/2] drm/i915: add render state initialization Mika Kuoppala
2014-05-06 13:41   ` Chris Wilson
2014-05-06 14:30     ` [PATCH v3 " Mika Kuoppala
2014-05-14 10:24       ` Mateo Lozano, Oscar
2014-05-14 11:13         ` Damien Lespiau [this message]
2014-05-14 11:24           ` Mateo Lozano, Oscar
2014-05-06 14:34     ` [PATCH v2 " Mika Kuoppala
2014-05-06 13:26 ` [PATCH v2 2/2] drm/i915: add null render states for gen6, gen7 and gen8 Mika Kuoppala
2014-05-06 13:39 ` [PATCH] tools/null_state_gen: generate null render state Mika Kuoppala
2014-05-06 13:47   ` Chris Wilson
2014-05-06 14:44     ` Mika Kuoppala
2014-05-09 15:15     ` Damien Lespiau
2014-05-08 14:37   ` Damien Lespiau
2014-05-08 14:43   ` Damien Lespiau
2014-05-08 15:10     ` Mika Kuoppala
2014-05-09 14:46   ` Damien Lespiau
2014-05-14 10:06   ` Damien Lespiau
2014-05-14 10:08 ` [PATCH v2 0/2] render state initialization (bdw rc6) Damien Lespiau

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=20140514111358.GC3022@strange.amr.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=ben@bwidawsk.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kristen@linux.intel.com \
    --cc=miku@iki.fi \
    --cc=oscar.mateo@intel.com \
    /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