From: "Bernatowicz, Marcin" <marcin.bernatowicz@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
igt-dev@lists.freedesktop.org,
Jakub Kolakowski <jakub1.kolakowski@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Lukasz Laguna <lukasz.laguna@intel.com>,
Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH i-g-t 1/2] tests/intel/xe_drm_fdinfo: Group utilization tests and skip when no utilization data
Date: Wed, 5 Mar 2025 17:31:43 +0100 [thread overview]
Message-ID: <609f3be5-d1f7-427b-b7ee-c7065c4a50d2@linux.intel.com> (raw)
In-Reply-To: <20250305121514.tojpbo7jlwbwcqt3@kamilkon-desk.igk.intel.com>
On 3/5/2025 1:15 PM, Kamil Konieczny wrote:
> Hi Marcin,
> On 2025-03-04 at 19:56:39 +0100, Marcin Bernatowicz wrote:
>> Wrap all utilization-related subtests in an igt_subtest_group and add
>> a fixture that ensures utilization data is available before running
>> them.
>>
>> Link: https://lore.kernel.org/r/20250205191644.2550879-1-marcin.bernatowicz@linux.intel.com
>>
>> Signed-off-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
>> Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: Lukasz Laguna <lukasz.laguna@intel.com>
>> Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>> ---
>> tests/intel/xe_drm_fdinfo.c | 122 ++++++++++++++++++++----------------
>> 1 file changed, 67 insertions(+), 55 deletions(-)
>>
>> diff --git a/tests/intel/xe_drm_fdinfo.c b/tests/intel/xe_drm_fdinfo.c
>> index 7330b4330..d18fe10d8 100644
>> --- a/tests/intel/xe_drm_fdinfo.c
>> +++ b/tests/intel/xe_drm_fdinfo.c
>> @@ -735,10 +735,6 @@ igt_main
>> igt_subtest("basic-mem")
>> basic_memory(xe);
>>
>> - igt_describe("Check if basic fdinfo content is present for engine utilization");
>> - igt_subtest("basic-utilization")
>> - basic_engine_utilization(xe);
>> -
>> igt_describe("Create and compare total and resident memory consumption by client");
>> igt_subtest("mem-total-resident")
>> mem_total_resident(xe);
>> @@ -751,57 +747,73 @@ igt_main
> [...]
>
>> + igt_subtest_group {
>> + igt_fixture {
>> + struct drm_client_fdinfo info = { };
>> +
>> + igt_require(igt_parse_drm_fdinfo(xe, &info, engine_map,
>> + ARRAY_SIZE(engine_map),
>> + NULL, 0));
>
> Problem with require placed here is that it will trigger also
> for all other test outside of group. That will clobber output.
Does it mean the igt_subtest_group is deprecated and the description
no more valid ?
"
/**
* igt_subtest_group:
...
* This macro allows to group together a set of #igt_fixture and #igt_subtest
* clauses. If any common setup in a fixture fails, only the subtests
in this
* group will fail or skip. Subtest groups can be arbitrarily nested.
"
>
>> + igt_require(info.num_engines);
>
> Both these should be placed in each subtest wrapped in function
> (see below) but imho this looks like a global requires at begin
> of a test? Or am I missing something?
>
>> + }
>> +
>
> Create function like:
>
> void require_utilization(int xe, ... engine_map)
> {
> struct drm_client_fdinfo info = { };
>
> igt_require(igt_parse_drm_fdinfo(xe, &info, engine_map,
> ARRAY_SIZE(engine_map),
> NULL, 0));
> igt_require(info.num_engines);
> }
>
> and use it in each utulization subtest like:
>
> igt_describe("Check if basic fdinfo content is present for engine utilization");
> igt_subtest("basic-utilization") {
> require_utilization(xe);
> basic_engine_utilization(xe);
> }
That is the repetition I wanted to avoid ;)
---
marcin
>
> Regards,
> Kamil
>
>> + igt_describe("Check if basic fdinfo content is present for engine utilization");
>> + igt_subtest("basic-utilization")
>> + basic_engine_utilization(xe);
>> +
>
> [...]
>
next prev parent reply other threads:[~2025-03-05 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 18:56 [PATCH i-g-t 0/2] tests/xe_drm_fdinfo: Check prerequisites for utilization tests Marcin Bernatowicz
2025-03-04 18:56 ` [PATCH i-g-t 1/2] tests/intel/xe_drm_fdinfo: Group utilization tests and skip when no utilization data Marcin Bernatowicz
2025-03-05 12:15 ` Kamil Konieczny
2025-03-05 16:31 ` Bernatowicz, Marcin [this message]
2025-03-06 10:56 ` Kamil Konieczny
2025-03-05 17:08 ` Lucas De Marchi
2025-03-06 9:19 ` Bernatowicz, Marcin
2025-03-13 4:19 ` Lucas De Marchi
2025-03-13 11:37 ` Zbigniew Kempczyński
2025-03-04 18:56 ` [PATCH i-g-t 2/2] tests/intel/xe_drm_fdinfo: Fail basic_engine_utilization if " Marcin Bernatowicz
2025-03-05 8:05 ` ✓ Xe.CI.BAT: success for tests/xe_drm_fdinfo: Check prerequisites for utilization tests (rev2) Patchwork
2025-03-05 8:35 ` ✓ i915.CI.BAT: " Patchwork
2025-03-05 9:02 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-05 12:34 ` ✗ i915.CI.Full: " 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=609f3be5-d1f7-427b-b7ee-c7065c4a50d2@linux.intel.com \
--to=marcin.bernatowicz@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=lukasz.laguna@intel.com \
--cc=umesh.nerlige.ramappa@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