From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] test/i915: gem_ctx_exec: Fix for using context engine map
Date: Tue, 19 Nov 2019 11:15:08 +0000 [thread overview]
Message-ID: <8b5fb952-c8ab-9203-ba77-9debaec72589@linux.intel.com> (raw)
In-Reply-To: <20191119110117.13209-1-venkata.s.dhanalakota@intel.com>
On 19/11/2019 11:01, Venkata Sandeep Dhanalakota wrote:
> Since engines are now looked up based on context engine map,
> context should be setup with engines before using in execbuf.
>
> Fixes: 1a7f2e59 igt("gem_ctx_exec: use the gem_engine_topology"
>
> Cc: Andi Shyti <andi.shyti@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Signed-off-by: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
> ---
> tests/i915/gem_ctx_exec.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/i915/gem_ctx_exec.c b/tests/i915/gem_ctx_exec.c
> index 6c2cd922..2bf47cf2 100644
> --- a/tests/i915/gem_ctx_exec.c
> +++ b/tests/i915/gem_ctx_exec.c
> @@ -132,6 +132,7 @@ static void invalid_context(int fd, const struct intel_execution_engine2 *e,
> gem_execbuf(fd, &execbuf);
>
> ctx = gem_context_create(fd);
> + gem_context_set_all_engines(fd, ctx);
> i915_execbuffer2_set_context_id(execbuf, ctx);
> gem_execbuf(fd, &execbuf);
>
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-11-19 11:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 11:01 [igt-dev] [PATCH i-g-t 1/2] test/i915: gem_ctx_exec: Fix for using context engine map Venkata Sandeep Dhanalakota
2019-11-19 11:01 ` [igt-dev] [PATCH i-g-t 2/2] test/i915: gem_exec_parallel: " Venkata Sandeep Dhanalakota
2019-11-19 11:11 ` Chris Wilson
2019-11-19 11:22 ` Tvrtko Ursulin
2019-11-19 11:36 ` Chris Wilson
2019-11-19 18:47 ` Venkata Sandeep Dhanalakota
2019-11-20 9:13 ` Tvrtko Ursulin
2019-11-20 9:35 ` Chris Wilson
2019-11-20 10:18 ` Tvrtko Ursulin
2019-11-20 15:22 ` Venkata Sandeep Dhanalakota
2019-11-19 11:16 ` Tvrtko Ursulin
2019-11-19 11:08 ` [igt-dev] [PATCH i-g-t 1/2] test/i915: gem_ctx_exec: " Chris Wilson
2019-11-19 11:24 ` Tvrtko Ursulin
2019-11-19 11:35 ` Chris Wilson
2019-11-19 11:41 ` Tvrtko Ursulin
2019-11-19 11:15 ` Tvrtko Ursulin [this message]
2019-11-19 11:57 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] " Patchwork
2019-11-19 16:40 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=8b5fb952-c8ab-9203-ba77-9debaec72589@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=venkata.s.dhanalakota@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