From: Ben Widawsky <benjamin.widawsky@intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] tools/null_state/gen9: Send atleast one valid component in VF state
Date: Wed, 5 Aug 2015 11:17:04 -0700 [thread overview]
Message-ID: <20150805181702.GA16230@intel.com> (raw)
In-Reply-To: <87k2takv9h.fsf@gaia.fi.intel.com>
On Wed, Aug 05, 2015 at 11:13:46AM +0300, Mika Kuoppala wrote:
> Ben Widawsky <benjamin.widawsky@intel.com> writes:
>
> > On Fri, Jul 31, 2015 at 04:27:07PM +0100, Arun Siluvery wrote:
> >> A programming restriction exists for this instruction, atleast one component
> >> of one valid vertex element must be enabled.
> >>
> >> Cc: Ben Widawsky <benjamin.widawsky@intel.com>
> >> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> >> Signed-off-by: Arun Siluvery <arun.siluvery@linux.intel.com>
> >> ---
> >> tools/null_state_gen/intel_renderstate_gen9.c | 7 ++++++-
> >> 1 file changed, 6 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/tools/null_state_gen/intel_renderstate_gen9.c b/tools/null_state_gen/intel_renderstate_gen9.c
> >> index 6f808f8..b3766ea 100644
> >> --- a/tools/null_state_gen/intel_renderstate_gen9.c
> >> +++ b/tools/null_state_gen/intel_renderstate_gen9.c
> >> @@ -440,7 +440,12 @@ int gen9_setup_null_render_state(struct intel_batchbuffer *batch)
> >> /* Vertex buffers */
> >> gen8_emit_vertex_buffers(batch);
> >> gen8_emit_vertex_elements(batch);
> >> - OUT_CMD(GEN9_3DSTATE_COMPONENT_PACKING, 5);
> >> +
> >> + OUT_BATCH(GEN9_3DSTATE_COMPONENT_PACKING | 3);
> >> + OUT_BATCH(1);
> >> + OUT_BATCH(0);
> >> + OUT_BATCH(0);
> >> + OUT_BATCH(0);
> >>
> >> OUT_BATCH(GEN6_3DSTATE_VF_STATISTICS | 1 /* Enable */);
> >>
> >
> > Like I said on IRC, I don't think this does anything unless you set bit 9 of
> > 3DSTATE_VF.0. Also, I believe you should be setting 0xf, not 1 since you'd want
> > to use all 4 components.
> >
> > So I'm not really sure what we're aiming to do. If you make it 0xf, and add a
> > comment about how this command doesn't do anything because we're not setting up
> > 3DSTATE_VF packing, it's:
> > Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
> >
> > I'm still more in favor of dropping the command altogether, that too would be:
> > Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
>
> We are trying here just to satisfy the minimum requirements the bspec
> states.
>
Right, except I am saying at least set minimal state which makes sense. Packing
1 component of the vertex element makes little sense (though doing this at all
makes even less sense).
> The bspec also states that with gen9+, the 3d pipeline state
> doesn't need to be initialized. We should seek confirmation
> about this and if it is so, remove the null state for gen9+.
>
That would be super terrific.
> -Mika
>
> >
> > --
> > Ben Widawsky, Intel Open Source Technology Center
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ben Widawsky, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-05 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 15:27 [PATCH] tools/null_state/gen9: Send atleast one valid component in VF state Arun Siluvery
2015-07-31 15:28 ` [PATCH] drm/i915/gen9: Update null batch to follow VF state restriction Arun Siluvery
2015-08-05 1:37 ` Ben Widawsky
2015-08-05 7:07 ` Mika Kuoppala
2015-08-10 21:39 ` shuang.he
2015-08-04 14:03 ` [PATCH] tools/null_state/gen9: Send atleast one valid component in VF state Mika Kuoppala
2015-08-05 1:36 ` Ben Widawsky
2015-08-05 8:13 ` Mika Kuoppala
2015-08-05 18:17 ` Ben Widawsky [this message]
2015-08-13 12:30 ` Mika Kuoppala
2015-08-13 13:11 ` [PATCH] tools/null_state/gen9: Send all components " Mika Kuoppala
2015-08-17 16:54 ` Ben Widawsky
2015-11-06 22:00 ` Chris Wilson
2015-11-06 22:19 ` Ben Widawsky
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=20150805181702.GA16230@intel.com \
--to=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.