Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	igt-dev@lists.freedesktop.org, Nirmoy Das <nirmoy.das@intel.com>,
	andi.shyti@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] tests/intel/gem_ctx_shared: Skip some test on MTL
Date: Thu, 14 Sep 2023 21:13:03 +0200	[thread overview]
Message-ID: <d316ffbd-a4dd-66f6-5455-254d9404e51f@linux.intel.com> (raw)
In-Reply-To: <20230914135017.el7yfodk4di4zqer@kamilkon-desk.igk.intel.com>

Hi Kamil,

On 9/14/2023 3:50 PM, Kamil Konieczny wrote:
> Hi Nirmoy,
>
> On 2023-09-13 at 11:42:51 +0200, Nirmoy Das wrote:
>> We do GGTT update on MTL using bcs engine, blocking that would
>> will fail the test so skip such subtests on bcs engine for MTL.
>>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>>   tests/intel/gem_ctx_shared.c | 12 ++++++++----
>>   1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/tests/intel/gem_ctx_shared.c b/tests/intel/gem_ctx_shared.c
>> index d24ae5483..bad032417 100644
>> --- a/tests/intel/gem_ctx_shared.c
>> +++ b/tests/intel/gem_ctx_shared.c
>> @@ -1105,22 +1105,26 @@ igt_main
>>   
>>   			igt_subtest_with_dynamic("Q-independent") {
>>   				for_each_queue(e, i915, &cfg)
>> -					independent(i915, &cfg, e, 0);
>> +					if (!(gem_has_ggtt_bind(i915) && e->class == I915_ENGINE_CLASS_COPY))
> ------------------------- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> imho it is better to make it a bool function (preferable) or macro
> and use it like:
> 					if (can_use_engine(i915, e))
>
> bool can_use_engine(int fd, engine *e)
> {
>      return !(e->class == I915_ENGINE_CLASS_COPY && gem_has_ggtt_bind(i915));
> }
>
> Same goes for your last patch, name of this function could be
> better.


Will do that in next rev.


Thanks,

Nirmoy

> Regards,
> Kamil
>
>> +						independent(i915, &cfg, e, 0);
>>   			}
>>   
>>   			igt_subtest_with_dynamic("Q-in-order") {
>>   				for_each_queue(e, i915, &cfg)
>> -					reorder(i915, &cfg, e->flags, EQUAL);
>> +					if (!(gem_has_ggtt_bind(i915) && e->class == I915_ENGINE_CLASS_COPY))
>> +						reorder(i915, &cfg, e->flags, EQUAL);
>>   			}
>>   
>>   			igt_subtest_with_dynamic("Q-out-order") {
>>   				for_each_queue(e, i915, &cfg)
>> -					reorder(i915, &cfg, e->flags, 0);
>> +					if (!(gem_has_ggtt_bind(i915) && e->class == I915_ENGINE_CLASS_COPY))
>> +						reorder(i915, &cfg, e->flags, 0);
>>   			}
>>   
>>   			igt_subtest_with_dynamic("Q-promotion") {
>>   				for_each_queue(e, i915, &cfg)
>> -					promotion(i915, &cfg, e->flags);
>> +					if (!(gem_has_ggtt_bind(i915) && e->class == I915_ENGINE_CLASS_COPY))
>> +						promotion(i915, &cfg, e->flags);
>>   			}
>>   		}
>>   
>> -- 
>> 2.41.0
>>

  reply	other threads:[~2023-09-14 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13  9:42 [igt-dev] [PATCH i-g-t 0/3] Ignore some tests on MTL which Nirmoy Das
2023-09-13  9:42 ` [igt-dev] [PATCH i-g-t 1/3] lib/igt_gt: Add a method to detect ggtt bind Nirmoy Das
2023-09-14 13:31   ` Kamil Konieczny
2023-09-14 19:13     ` Nirmoy Das
2023-09-13  9:42 ` [igt-dev] [PATCH i-g-t 2/3] tests/intel/gem_ctx_shared: Skip some test on MTL Nirmoy Das
2023-09-14 13:50   ` Kamil Konieczny
2023-09-14 19:13     ` Nirmoy Das [this message]
2023-09-13  9:42 ` [igt-dev] [PATCH i-g-t 3/3] tests/intel/gem_ctx_schedule: " Nirmoy Das
2023-09-13 10:54 ` [igt-dev] ✗ Fi.CI.BAT: failure for Ignore some tests on MTL which (rev2) Patchwork
2023-09-13 11:51 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-09-14 20:18 [igt-dev] [PATCH i-g-t v2 0/3] Ignore some tests on MTL which Nirmoy Das
2023-09-14 20:18 ` [igt-dev] [PATCH i-g-t 2/3] tests/intel/gem_ctx_shared: Skip some test on MTL Nirmoy Das
2023-09-15 18:02   ` Kamil Konieczny

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=d316ffbd-a4dd-66f6-5455-254d9404e51f@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=andi.shyti@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=nirmoy.das@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