From: Damien Lespiau <damien.lespiau@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Imre Deak <imre.deak@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [igt PATCH] gen9: fix gem_render_copy 3d state setup
Date: Thu, 29 Jan 2015 11:37:01 +0000 [thread overview]
Message-ID: <20150129113700.GD31728@strange.ger.corp.intel.com> (raw)
In-Reply-To: <20150129113246.GM25850@nuc-i3427.alporthouse.com>
On Thu, Jan 29, 2015 at 11:32:46AM +0000, Chris Wilson wrote:
> On Thu, Jan 29, 2015 at 11:17:04AM +0000, Damien Lespiau wrote:
> > On Thu, Jan 29, 2015 at 11:12:46AM +0000, Chris Wilson wrote:
> > > On Thu, Jan 29, 2015 at 03:01:50AM -0800, Imre Deak wrote:
> > > > On Thu, 2015-01-29 at 10:51 +0000, Damien Lespiau wrote:
> > > > > On Thu, Jan 29, 2015 at 12:03:19AM -0800, Imre Deak wrote:
> > > > > > Without emitting the default 3DSTATE_WM_DEPTH_STENCIL state the test
> > > > > > will fail.
> > > > > >
> > > > > > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > > > >
> > > > > Question: Wasn't the golden context supposed to paper over those?
> > > >
> > > > Perhaps, currently the golden context doesn't include this.
> > >
> > > Today, you cannot rely on the initial contents of the context even with
> > > the golden render state. There is no pristine context, every client is
> > > responsible for configuring the hardware exactly as they intend to use -
> > > at least as regards the untrusted commands (e.g. 3DSTATE).
> >
> > Right. Now the question is, do we want to change that and have the
> > golden context with sane defaults?
>
> You missed the point. The point is that we don't keep initialise every
> context from scratch. And there still doesn't seem to be any reason to
> be papering over userspace bugs.
That's because I still think the end of the journey is a fully
initialized golden context image + copy of that context on context
creation.
--
Damien
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-29 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 8:03 [igt PATCH] gen9: fix gem_render_copy 3d state setup Imre Deak
2015-01-29 10:51 ` Damien Lespiau
2015-01-29 11:01 ` Imre Deak
2015-01-29 11:12 ` Chris Wilson
2015-01-29 11:17 ` Damien Lespiau
2015-01-29 11:32 ` Chris Wilson
2015-01-29 11:37 ` Damien Lespiau [this message]
2015-01-29 14:15 ` Mika Kuoppala
2015-01-30 16:22 ` Daniel Vetter
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=20150129113700.GD31728@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=imre.deak@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