public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	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:41:46 +0000	[thread overview]
Message-ID: <c300efbe-d283-1b83-434c-23b7bcfc5edc@linux.intel.com> (raw)
In-Reply-To: <157416330678.10169.7529772480987205839@skylake-alporthouse-com>


On 19/11/2019 11:35, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-11-19 11:24:17)
>>
>> On 19/11/2019 11:08, Chris Wilson wrote:
>>> Quoting Venkata Sandeep Dhanalakota (2019-11-19 11:01:16)
>>>> 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);
>>>
>>> Irrelevant.
>>
>> I guess it is a bit, but it completes the test conversion to be correct.
>> You would want to split the legacy-vs-new engine selection in this one?
> 
> No, there shouldn't be a per-engine component to this test at all.
> The way we have separated the context state is that it is akin to the
> process state. Now whether or not the context has an engine is another
> question (and answered elsewhere), the question is most certainly not
> whether an engine has a context as is being asked here.

Okay, option 3, drop the per-engine nature of this subtest altogether.

Regards,

Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-11-19 11:54 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 [this message]
2019-11-19 11:15 ` Tvrtko Ursulin
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=c300efbe-d283-1b83-434c-23b7bcfc5edc@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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