From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org, miku@iki.fi,
rafael.barbalho@intel.com
Subject: Re: [RFC 0/3] render state initialization (bdw rc6)
Date: Wed, 23 Apr 2014 11:04:48 -0700 [thread overview]
Message-ID: <20140423180448.GD25941@bwidawsk.net> (raw)
In-Reply-To: <20140422205156.GA22645@nuc-i3427.alporthouse.com>
On Tue, Apr 22, 2014 at 09:51:56PM +0100, Chris Wilson wrote:
> On Tue, Apr 22, 2014 at 08:19:41PM +0300, Mika Kuoppala wrote:
> > Hi,
> >
> > Here are patches to initialize first render context to a hopefully,
> > valid state. If pipeline/context is not initialized and we enter rc6 on bdw,
> > the render ring can hung on the first batch submitted. That is atleast
> > the hypothesis this work is based on.
> >
> > The states are stripped from rendercopy_genX's from i-g-t/lib and
> > the state generators are part of i-g-t also. The states are
> > propably overshoot from what can be consider the minimal valid
> > (null) state on the pipeline. I just initialized everything rendercopy
> > does and haven't really put effort on optimizing the state until
> > I get some test results that this indeed solves anything.
> >
> > The state generators can be found here but they are not needed for testing.
> > http://cgit.freedesktop.org/~miku/intel-gpu-tools/log/?h=null_state_gen
> >
> > Gen7 and Gen8 seems to atleast survive the boot but Gen6 is totally
> > untested.
> >
> > Here is the branch for testing:
> > http://cgit.freedesktop.org/~miku/drm-intel/log/?h=render_state
> >
> > I am interested to know if these patches make matters better/worse for those
> > who have issues with first batch hanging on bdw, but as always, any feedback
> > is greatly appreciated.
> >
> > Mika Kuoppala (3):
> > drm/i915: export vmap_batch from command parser
> It's only a single page, it does not need to be vmapped.
>
> > drm/i915: add render state initialization
> > drm/i915: add null render states for gen6, gen7 and gen8
>
> I still don't buy that this is anything more than papering over a
> problem. The state you load into the context is invalid as soon as it is
> executed, which may lead to problems, we don't know since the problem is
> not being discussed, and it will certainly be more explicit if the right
> bits are poked into the context directly to keep the hw from falling over.
> -Chris
>
Paper is better than no paper. Anyway there are a couple of units where
we know NULL is better than not NULL (VFE is one). I have been unable to
get an exact reason why this is needed so that we know exactly what to
fix. It has been a very frustrating experience.
We could try to get info on what Windows does, but we may not be able to
get a, "why."
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-04-23 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 17:19 [RFC 0/3] render state initialization (bdw rc6) Mika Kuoppala
2014-04-22 17:19 ` [PATCH 1/3] drm/i915: export vmap_batch from command parser Mika Kuoppala
2014-04-22 17:19 ` [PATCH 2/3] drm/i915: add render state initialization Mika Kuoppala
2014-04-22 20:26 ` Daniel Vetter
2014-05-06 1:20 ` Ben Widawsky
2014-05-06 13:33 ` Mika Kuoppala
2014-04-22 17:19 ` [PATCH 3/3] drm/i915: add null render states for gen6, gen7 and gen8 Mika Kuoppala
2014-05-02 20:43 ` Damien Lespiau
2014-05-02 22:09 ` Damien Lespiau
2014-04-22 20:51 ` [RFC 0/3] render state initialization (bdw rc6) Chris Wilson
2014-04-23 18:04 ` Ben Widawsky [this message]
2014-04-24 18:51 ` Kristen Carlson Accardi
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=20140423180448.GD25941@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
--cc=miku@iki.fi \
--cc=rafael.barbalho@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