From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] tests: Add gem_exec_params
Date: Thu, 24 Apr 2014 10:55:47 +0300 [thread overview]
Message-ID: <20140424075547.GN18465@intel.com> (raw)
In-Reply-To: <CAKMK7uHdq8JEsE6DEs2x5zCMP0xUi1Fiyd+APjJoYaf_tvaNwg@mail.gmail.com>
On Thu, Apr 24, 2014 at 09:18:24AM +0200, Daniel Vetter wrote:
> On Thu, Apr 24, 2014 at 8:43 AM, Zhao Yakui <yakui.zhao@intel.com> wrote:
> > On Wed, 2014-04-23 at 12:32 -0600, Daniel Vetter wrote:
> >> + igt_subtest("rel-constants-invalid") {
> >> + execbuf.flags = I915_EXEC_RENDER | (I915_EXEC_CONSTANTS_REL_SURFACE+1);
> >> + RUN_FAIL(EINVAL);
> >
> > It seems that the exec.flags is the same as "I915_EXEC_BSD |
> > I915_EXEC_CONSTANTS_REL_SURFACE). And then it is similar to subtest of
> > rel-constants-invalid-ring. Not sure whether you are hoping to set the
> > flag as "I915_EXEC_RENDER | I915_EXEC_CONSTANTS_MASK"?
>
> They're three completely different checks:
> 1. checks for invalid flags on rings other than RENDER
> 2. checks for a specific invalid flag which doesn't exist on gen5+ any more
> 3. checks for a completely invalid flag (notice the + 1) on any platform
I think the point was that I915_EXEC_RENDER+1 == I915_EXEC_BSD. Hence
the +1 is entirely bogus. So you want either
I915_EXEC_CONSTANTS_REL_SURFACE+(1<<6) or just
I915_EXEC_CONSTANTS_MASK.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-04-24 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 18:32 [PATCH] tests: Add gem_exec_params Daniel Vetter
2014-04-24 6:43 ` Zhao Yakui
2014-04-24 7:18 ` Daniel Vetter
2014-04-24 7:55 ` Ville Syrjälä [this message]
2014-04-24 8:46 ` [PATCH] tests/gem_exec_params: Fix rel-constants-invalid subtest Daniel Vetter
2014-04-24 10:05 ` [PATCH] tests: Add gem_exec_params Daniel Vetter
2014-04-24 8:27 ` Zhao Yakui
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=20140424075547.GN18465@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--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 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.