From: "Thasleem, Mohammed" <mohammed.thasleem@intel.com>
To: "Michał Grzelak" <michal.grzelak@intel.com>,
igt-dev@lists.freedesktop.org
Cc: <swati2.sharma@intel.com>
Subject: Re: [PATCH i-g-t v5 1/4] tests/kms_flip: test suspend on one pair of pipes
Date: Mon, 23 Feb 2026 16:46:01 +0530 [thread overview]
Message-ID: <2c82ba5b-b38c-46eb-8956-710836fdbc85@intel.com> (raw)
In-Reply-To: <20260213084930.252273-2-michal.grzelak@intel.com>
On 13-02-2026 02:19 pm, Michał Grzelak wrote:
> Currently, every pair of ({pipe1, pipe2}, {output1, output2}) is being
> tested in 2x-* subtests. Since suspend shouldn't be tested per pipe, it
> causes unnecessary overhead: with 4 pipes & 4 displays it runs up to 36
> tests. Given that each suspend's dynamic subtest can take up to tens of
> seconds, total duration of the test easily exceeds timeout.
>
> When testing suspend, for each pair of outputs test only first and last
> pipe unless it is said to run on all pipes.
>
> Signed-off-by: Michał Grzelak <michal.grzelak@intel.com>
> ---
> tests/kms_flip.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_flip.c b/tests/kms_flip.c
> index 49a5f4ed1..8bda82627 100755
> --- a/tests/kms_flip.c
> +++ b/tests/kms_flip.c
> @@ -1918,6 +1918,12 @@ static void run_pair(int duration, int flags)
> for (n = 0; n < resources->count_crtcs; n++) {
> for (j = i + 1; j < resources->count_connectors; j++) {
> for (m = n + 1; m < resources->count_crtcs; m++) {
> + /* Limit the execution to 2 CRTCs (first & last) for hang and suspend tests */
> + if (((flags & TEST_HANG) || (flags & TEST_SUSPEND)) && !all_crtcs &&
> + ((n != 0 && n != resources->count_crtcs) ||
-->looks like needed to crrect n boundary check from count_crtcs to
count_crtcs-1 to match loop range, plese check it..
> + m != resources->count_crtcs - 1))
> + continue;
> +
> memset(&o, 0, sizeof(o));
> o.count = 2;
> o._connector[0] = resources->connectors[i];
> @@ -1963,8 +1969,8 @@ static void run_pair(int duration, int flags)
> crtc_idxs[0] = n;
> crtc_idxs[1] = m;
>
> - /* Limit the execution to 2 CRTCs (first & last) for hang tests */
> - if ((flags & TEST_HANG) && !all_crtcs &&
> + /* Limit the execution to 2 CRTCs (first & last) for hang and suspend tests */
> + if (((flags & TEST_HANG) || (flags & TEST_SUSPEND)) && !all_crtcs &&
> ((n != 0 && n != resources->count_crtcs) ||
-->here aswell..
> m != resources->count_crtcs - 1))
> continue;
next prev parent reply other threads:[~2026-02-23 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 8:49 [PATCH i-g-t v5 0/4] kms_flip: limit number of subtests run Michał Grzelak
2026-02-13 8:49 ` [PATCH i-g-t v5 1/4] tests/kms_flip: test suspend on one pair of pipes Michał Grzelak
2026-02-23 11:16 ` Thasleem, Mohammed [this message]
2026-02-13 8:49 ` [PATCH i-g-t v5 2/4] tests/kms_flip: run suspend tests on one pipe per output Michał Grzelak
2026-02-23 11:26 ` Thasleem, Mohammed
2026-02-13 8:49 ` [PATCH i-g-t v5 3/4] tests/kms_flip: limit output pairs when testing suspend Michał Grzelak
2026-02-23 15:25 ` Thasleem, Mohammed
2026-02-13 8:49 ` [PATCH i-g-t v5 4/4] tests/kms_flip: limit number of outputs wrt suspend Michał Grzelak
2026-02-23 17:24 ` Thasleem, Mohammed
2026-02-13 10:57 ` ✓ Xe.CI.BAT: success for kms_flip: limit number of subtests run (rev4) Patchwork
2026-02-13 11:14 ` ✗ i915.CI.BAT: failure " Patchwork
2026-02-14 7:05 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-16 8:21 ` ✓ Xe.CI.BAT: success for kms_flip: limit number of subtests run (rev5) Patchwork
2026-02-16 8:43 ` ✓ i915.CI.BAT: " Patchwork
2026-02-16 9:20 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-16 10:44 ` Michał Grzelak
2026-02-16 10:29 ` ✗ i915.CI.Full: " Patchwork
2026-02-16 10:56 ` Michał Grzelak
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=2c82ba5b-b38c-46eb-8956-710836fdbc85@intel.com \
--to=mohammed.thasleem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=michal.grzelak@intel.com \
--cc=swati2.sharma@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