From: Nidhi Gupta <nidhi1.gupta@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Nidhi Gupta <nidhi1.gupta@intel.com>
Subject: [igt-dev] [PATCH v4 3/7] tests/kms_pipe_crc_basic: Limit the execution to two pipes
Date: Thu, 2 Feb 2023 10:45:05 +0530 [thread overview]
Message-ID: <20230202051509.28983-4-nidhi1.gupta@intel.com> (raw)
In-Reply-To: <20230202051509.28983-1-nidhi1.gupta@intel.com>
From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
As the execution is taking more time, limit the execution to two (first
& last) pipes.
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
---
tests/kms_pipe_crc_basic.c | 41 +++++++++++++++++++++++++++++++++++++-
1 file changed, 40 insertions(+), 1 deletion(-)
diff --git a/tests/kms_pipe_crc_basic.c b/tests/kms_pipe_crc_basic.c
index 91a1b8ab..97b97863 100644
--- a/tests/kms_pipe_crc_basic.c
+++ b/tests/kms_pipe_crc_basic.c
@@ -30,6 +30,7 @@
#include <string.h>
#include <fcntl.h>
+static bool extended = false;
typedef struct {
int drm_fd;
@@ -276,7 +277,23 @@ static void test_disable_crc_after_crtc(data_t *data, enum pipe pipe,
data_t data = {0, };
-igt_main
+static int opt_handler(int opt, int opt_index, void *_data)
+{
+ switch (opt) {
+ case 'e':
+ extended = true;
+ break;
+ default:
+ return IGT_OPT_HANDLER_ERROR;
+ }
+
+ return IGT_OPT_HANDLER_SUCCESS;
+}
+
+const char *help_str =
+ " -e \tExtended tests.\n";
+
+igt_main_args("e", NULL, help_str, opt_handler, NULL)
{
enum pipe pipe;
igt_output_t *output;
@@ -298,6 +315,8 @@ igt_main
{ "hang-read-crc", TEST_HANG,
"Hang test for pipe CRC read." },
};
+ enum pipe active_pipes[IGT_MAX_PIPES];
+ uint32_t last_pipe = 0;
int i;
igt_fixture {
@@ -312,6 +331,11 @@ igt_main
igt_require_pipe_crc(data.drm_fd);
data.debugfs = igt_debugfs_dir(data.drm_fd);
+
+ /* Get active pipes. */
+ for_each_pipe(&data.display, pipe)
+ active_pipes[last_pipe++] = pipe;
+ last_pipe--;
}
igt_describe("Tests error handling when the bad source is set.");
@@ -322,6 +346,11 @@ igt_main
igt_describe(tests[i].desc);
igt_subtest_with_dynamic(tests[i].name) {
for_each_pipe_with_single_output(&data.display, pipe, output) {
+ if (igt_run_in_simulation() && !extended &&
+ pipe != active_pipes[0] &&
+ pipe != active_pipes[last_pipe])
+ continue;
+
igt_dynamic_f("pipe-%s-%s", kmstest_pipe_name(pipe), output->name) {
if (tests[i].flags & TEST_SUSPEND) {
test_read_crc(&data, pipe, output, 0);
@@ -350,6 +379,11 @@ igt_main
"does not cause issues.");
igt_subtest_with_dynamic("disable-crc-after-crtc") {
for_each_pipe_with_single_output(&data.display, pipe, output) {
+ if (igt_run_in_simulation() && !extended &&
+ pipe != active_pipes[0] &&
+ pipe != active_pipes[last_pipe])
+ continue;
+
igt_dynamic_f("pipe-%s-%s", kmstest_pipe_name(pipe), output->name)
test_disable_crc_after_crtc(&data, pipe, output);
}
@@ -358,6 +392,11 @@ igt_main
igt_describe("Basic sanity check for CRC mismatches");
igt_subtest_with_dynamic("compare-crc-sanitycheck") {
for_each_pipe_with_single_output(&data.display, pipe, output) {
+ if (igt_run_in_simulation() && !extended &&
+ pipe != active_pipes[0] &&
+ pipe != active_pipes[last_pipe])
+ continue;
+
igt_dynamic_f("pipe-%s-%s", kmstest_pipe_name(pipe), output->name)
test_compare_crc(&data, pipe, output);
}
--
2.39.0
next prev parent reply other threads:[~2023-02-02 5:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 5:15 [igt-dev] [PATCH v4 0/7] Limit the execution to few pipes/planes Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 1/7] tests/i915/kms_draw_crc: Ignore RGB565 & XRGB2101010 formats on simulation Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 2/7] tests/kms_async_flips: Limit the execution to single pipe Nidhi Gupta
2023-02-02 5:15 ` Nidhi Gupta [this message]
2023-02-02 10:33 ` [igt-dev] [PATCH v4 3/7] tests/kms_pipe_crc_basic: Limit the execution to two pipes Modem, Bhanuprakash
2023-02-03 2:15 ` [igt-dev] [PATCH v5 " Nidhi Gupta
2023-02-03 5:49 ` [igt-dev] [i-g-t V3 " Bhanuprakash Modem
2023-02-02 5:15 ` [igt-dev] [PATCH v4 4/7] tests/kms_plane_alpha_blend: Limit the execution to single pipe & two planes Nidhi Gupta
2023-02-02 6:01 ` [igt-dev] [PATCH v5 " Nidhi Gupta
2023-02-02 7:00 ` Nidhi Gupta
2023-02-02 15:00 ` Kamil Konieczny
2023-02-02 5:15 ` [igt-dev] [PATCH v4 5/7] tests/kms_plane_cursor: Limit the execution to two pipes Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 6/7] tests/kms_plane_scaling: Limit the execution to two pipes/planes Nidhi Gupta
2023-02-02 5:15 ` [igt-dev] [PATCH v4 7/7] tests/i915/kms_frontbuffer_tracking: Reduce the execution time on simulation Nidhi Gupta
2023-02-02 5:51 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev2) Patchwork
2023-02-02 6:00 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Limit the execution to few pipes/planes (rev3) Patchwork
2023-02-02 6:00 ` [igt-dev] ✗ Fi.CI.BAT: failure for Limit the execution to few pipes/planes (rev2) Patchwork
2023-02-02 7:25 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev4) Patchwork
2023-02-02 7:26 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2023-02-02 15:45 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2023-02-03 2:40 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-03 7:16 ` [igt-dev] ✗ GitLab.Pipeline: warning for Limit the execution to few pipes/planes (rev6) Patchwork
2023-02-03 12:40 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-03 13:08 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes (rev6) Patchwork
2023-02-03 17:48 ` [igt-dev] ✓ Fi.CI.IGT: success for Limit the execution to few pipes/planes (rev5) Patchwork
2023-02-04 0:12 ` [igt-dev] ✓ Fi.CI.IGT: success for Limit the execution to few pipes/planes (rev6) 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=20230202051509.28983-4-nidhi1.gupta@intel.com \
--to=nidhi1.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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