From: Andi Shyti <andi.shyti@intel.com>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: igt-dev <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t v3] tests/i915/gem_spin_batch: Update with engine discovery
Date: Thu, 4 Jul 2019 16:11:27 +0300 [thread overview]
Message-ID: <20190704131127.GA3061@intel.intel> (raw)
In-Reply-To: <20190703065241.9964-1-ramalingam.c@intel.com>
Hi Ram,
On Wed, Jul 03, 2019 at 12:22:41PM +0530, Ramalingam C wrote:
> Legacy execbuf abi tests are prefixed with legacy. New test are added to
> run on physical engines accessed through engine discovery.
>
> So legacy tests run on the unconfigured (with engine map) context and
> use a new helper gem_eb_flags_to_engine to look up the engine from the
> intel_execution_engines2 static list. This is only to enable the
> core test code to be shared.
>
> Places where new contexts are created had to be updated to either
> equally configure the contexts or not.
>
> v2:
> helper called gem_engine_is_equal is added [tvrtko]
> rebased to adopt the changte in eb_flag to engine [tvrtko]
> v3:
> returned the result of the expression itself [tvrtko]
>
> Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Acked-by: Andi Shyti <andi.shyti@gmail.com>
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-07-04 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 6:52 [igt-dev] [PATCH i-g-t v3] tests/i915/gem_spin_batch: Update with engine discovery Ramalingam C
2019-07-03 14:37 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/gem_spin_batch: Update with engine discovery (rev3) Patchwork
2019-07-04 13:11 ` Andi Shyti [this message]
2019-07-04 13:56 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20190704131127.GA3061@intel.intel \
--to=andi.shyti@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ramalingam.c@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