public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
	Nidhi Gupta <nidhi1.gupta@intel.com>,
	<igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH v3 3/7] tests/kms_pipe_crc_basic: Limit the execution to two pipes
Date: Mon, 6 Feb 2023 10:55:51 +0530	[thread overview]
Message-ID: <bfb35eec-a882-7794-7e12-2f7097104762@intel.com> (raw)
In-Reply-To: <52d23cd1-742d-2504-ed60-91f840687777@intel.com>

Hi Ankit,

On Mon-06-02-2023 10:10 am, Nautiyal, Ankit K wrote:
> The help str can mention that option -e stands for execution on all pipes.
> 
> Also, there are tests that are restricted to 2 pipes only even on real 
> hardware, and have -e cmdline parameter to run on all pipes.
> 
> Should we just limit to 2 pipes by default, and drop is_simulation?

Intention of this patch is to restrict the execution on simulation as it 
is taking more time to execute which is causing CI timeout.

I don't see any value added to CI if we limit the execution to two pipes 
on real hardware. Since it is taking just few seconds to complete the 
execution.

Here we have a latest patch [1] where we mentioned about the option -e

[1]: https://patchwork.freedesktop.org/series/113635/

- Bhanu

> 
> Regards,
> 
> Ankit
> 
> 
> On 1/31/2023 7:06 PM, Nidhi Gupta wrote:
>> 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);
>>           }

  reply	other threads:[~2023-02-06  5:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 13:36 [igt-dev] [PATCH v3 0/7] Limit the execution to few pipes/planes Nidhi Gupta
2023-01-31 13:36 ` [igt-dev] [PATCH v3 1/7] tests/i915/kms_draw_crc: Ignore RGB565 & XRGB2101010 formats on simulation Nidhi Gupta
2023-01-31 13:36 ` [igt-dev] [PATCH v3 2/7] tests/kms_async_flips: Limit the execution to single pipe Nidhi Gupta
2023-01-31 13:36 ` [igt-dev] [PATCH v3 3/7] tests/kms_pipe_crc_basic: Limit the execution to two pipes Nidhi Gupta
2023-02-06  4:40   ` Nautiyal, Ankit K
2023-02-06  5:25     ` Modem, Bhanuprakash [this message]
2023-01-31 13:36 ` [igt-dev] [PATCH v3 4/7] tests/kms_plane_alpha_blend: Restrict the execution to 2 pipes and planes Nidhi Gupta
2023-01-31 13:36 ` [igt-dev] [PATCH v3 5/7] tests/kms_plane_cursor: Limit the execution to two pipes Nidhi Gupta
2023-01-31 13:36 ` [igt-dev] [PATCH v3 6/7] tests/kms_plane_scaling: Limit the execution to two pipes/planes Nidhi Gupta
2023-01-31 13:36 ` [igt-dev] [PATCH v3 7/7] tests/i915/kms_frontbuffer_tracking: Reduce the execution time on simulation Nidhi Gupta
2023-01-31 14:24 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the execution to few pipes/planes Patchwork
2023-01-31 19:15 ` [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=bfb35eec-a882-7794-7e12-2f7097104762@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=nidhi1.gupta@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