From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
IGT dev <igt-dev@lists.freedesktop.org>,
Andi Shyti <andi.shyti@linux.intel.com>,
Fei Yang <fei.yang@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Subject: Re: [igt-dev] [PATCH v3 1/1] test/gem_create: limit set_pat only to Meteor Lake
Date: Wed, 12 Jul 2023 09:09:55 +0100 [thread overview]
Message-ID: <500f3993-dc82-bc64-31b1-df7390164251@linux.intel.com> (raw)
In-Reply-To: <20230607085737.tgauj4s2pvbjx7rg@kamilkon-desk1>
On 07/06/2023 09:57, Kamil Konieczny wrote:
> On 2023-06-06 at 19:52:26 +0200, Andi Shyti wrote:
>> From: Fei Yang <fei.yang@intel.com>
>>
>> For platforms other than Meteor Lake the set_pat extension should
>> return -ENODEV.
>>
>> Signed-off-by: Fei Yang <fei.yang@intel.com>
>> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
>> ---
>> tests/i915/gem_create.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/tests/i915/gem_create.c b/tests/i915/gem_create.c
>> index e9e8216d2b..b7961d9ef2 100644
>> --- a/tests/i915/gem_create.c
>> +++ b/tests/i915/gem_create.c
>> @@ -657,6 +657,7 @@ static void create_ext_set_pat(int fd)
>> .base = { .name = I915_GEM_CREATE_EXT_SET_PAT },
>> .pat_index = 65,
>> };
>> + uint32_t devid = intel_get_drm_devid(fd);
>> struct drm_i915_gem_caching arg;
>> uint64_t size;
>> uint32_t handle;
>> @@ -672,6 +673,9 @@ static void create_ext_set_pat(int fd)
>> */
>> if (ret == -EINVAL)
>> igt_skip("I915_GEM_CREATE_EXT_SET_PAT is not supported\n");
>> + else if (!IS_METEORLAKE(devid))
>> + igt_assert_eq(ret, -ENODEV);
Hmm a sea of red..
https://intel-gfx-ci.01.org/tree/drm-tip/index.html?testfilter=set-pat
https://intel-gfx-ci.01.org/tree/drm-intel-fixes/CI_DIF_773/shard-snb7/igt@gem_create@create-ext-set-pat.html
Starting subtest: create-ext-set-pat
(gem_create:1095) CRITICAL: Test assertion failure function create_ext_set_pat, file ../../../usr/src/igt-gpu-tools/tests/i915/gem_create.c:679:
(gem_create:1095) CRITICAL: Failed assertion: ret == 0
Subtest create-ext-set-pat failed.
Not sure why shards run did not flag this (?!), but AFAICT the logic does not work.
It should be igt_skip on MTL, otherwise..
>> +
>
> lgtm,
>
> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>
>> igt_assert(ret == 0);
.. test just fails here. So something like:
igt_skip_on_f(ret == -EINVAL || (ret == -ENODEV && IS_METEORLAKE(devid)), "...")
?
Regards,
Tvrtko
>>
>> /*
>> --
>> 2.40.1
>>
next prev parent reply other threads:[~2023-07-12 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 17:52 [igt-dev] [PATCH v3 0/1] test/gem_create: limit set_pat only to Meteor Lake Andi Shyti
2023-06-06 17:52 ` [igt-dev] [PATCH v3 1/1] " Andi Shyti
2023-06-07 8:57 ` Kamil Konieczny
2023-07-12 8:09 ` Tvrtko Ursulin [this message]
2023-07-12 8:18 ` Andi Shyti
2023-06-06 18:38 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-07 7:46 ` [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=500f3993-dc82-bc64-31b1-df7390164251@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=fei.yang@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=tvrtko.ursulin@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