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 4/4] tests/kms_flip: limit number of outputs wrt suspend
Date: Mon, 23 Feb 2026 22:54:39 +0530 [thread overview]
Message-ID: <8e845be6-52dc-4dab-876b-f5a444636726@intel.com> (raw)
In-Reply-To: <20260213084930.252273-5-michal.grzelak@intel.com>
On 13-02-2026 02:19 pm, Michał Grzelak wrote:
> When running suspend subtests on single output, we can still hit the
> timeout by testing too much outputs. Default to testing 3 outputs. Add
> commandline parameter to run on all outputs.
-->Small wording nit: “commandline” --> “command-line”
> Signed-off-by: Michał Grzelak <michal.grzelak@intel.com>
> ---
> tests/kms_flip.c | 21 ++++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/tests/kms_flip.c b/tests/kms_flip.c
> index 1c8495ef1..80e42cabb 100755
> --- a/tests/kms_flip.c
> +++ b/tests/kms_flip.c
> @@ -264,12 +264,14 @@
> #define RUN_PAIR 2
>
> #define PAIR_LIMIT 3
> +#define CONN_LIMIT 3
>
> #ifndef DRM_CAP_TIMESTAMP_MONOTONIC
> #define DRM_CAP_TIMESTAMP_MONOTONIC 6
> #endif
>
> static bool all_crtcs = false;
> +static bool all_conns = false;
> static bool all_pairs = false;
>
> drmModeRes *resources;
> @@ -1822,6 +1824,7 @@ static void run_test(int duration, int flags)
> {
> struct test_output o;
> int i, n, modes = 0;
> + int conn_count = 0;
>
> /* No tiling support in XE. */
> if (is_xe_device(drm_fd) && flags & TEST_FENCE_STRESS)
> @@ -1887,6 +1890,10 @@ static void run_test(int duration, int flags)
> if ((flags & TEST_SUSPEND) && !all_crtcs && n != 0)
> continue;
>
> + /* Limit number of displays run */
> + if ((flags & TEST_SUSPEND) && !all_conns && conn_count >= CONN_LIMIT)
> + continue;
--> here can't we stop testing once we reach limit by return instead
continue?
> +
> memset(&o, 0, sizeof(o));
> o.count = 1;
> o._connector[0] = resources->connectors[i];
> @@ -1895,8 +1902,15 @@ static void run_test(int duration, int flags)
> o.depth = 24;
>
> crtc_idx = n;
> - run_test_on_crtc_set(&o, &crtc_idx, RUN_TEST,
> - resources->count_crtcs, duration);
> +
> + connector_find_preferred_mode(o._connector[0], n, &o);
> + if (o.mode_valid) {
> + run_test_on_crtc_set(&o, &crtc_idx, RUN_TEST,
> + resources->count_crtcs, duration);
> + conn_count++;
> + } else {
> + free_test_output(&o);
> + }
> }
> }
>
> @@ -2070,10 +2084,11 @@ static int opt_handler(int opt, int opt_index, void *data)
> }
>
> const char *help_str =
> + " -c \tRun on all connectors. (By default suspend subtests will run on 3 connectors)\n"
> " -e \tRun on all CRTCs. (By default subtests will run on two CRTCs)\n"
> " -p \tRun on all output pairs. (By default 2x-* suspend subtests will run on 3 pairs)\n";
>
> -int igt_main_args("ep", NULL, help_str, opt_handler, NULL)
> +int igt_main_args("cep", NULL, help_str, opt_handler, NULL)
> {
> struct {
> int duration;
next prev parent reply other threads:[~2026-02-23 17:24 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
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 [this message]
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=8e845be6-52dc-4dab-876b-f5a444636726@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