Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Gupta, Anshuman" <anshuman.gupta@intel.com>
Cc: "Latvala, Petri" <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] tests/kms_flip: Restrict the hang tests execution to two pipes
Date: Fri, 23 Jul 2021 05:34:45 +0000	[thread overview]
Message-ID: <be36f63b32a447d6a8cf39e123771764@intel.com> (raw)
In-Reply-To: <20210705125617.4631-3-bhanuprakash.modem@intel.com>



> -----Original Message-----
> From: Modem, Bhanuprakash <bhanuprakash.modem@intel.com>
> Sent: Monday, July 5, 2021 6:26 PM
> To: igt-dev@lists.freedesktop.org; Gupta, Anshuman <anshuman.gupta@intel.com>
> Cc: Modem, Bhanuprakash <bhanuprakash.modem@intel.com>; Shankar, Uma
> <uma.shankar@intel.com>; Latvala, Petri <petri.latvala@intel.com>; B S, Karthik
> <karthik.b.s@intel.com>
> Subject: [PATCH i-g-t 2/3] tests/kms_flip: Restrict the hang tests execution to two
> pipes
> 
> To save the CI execution time, instead of running on all pipes restrict the hang tests
> execution to two pipes (first & last).
> 
> If we want to execute on all pipes, we need to pass an extra argument "-e" indicates
> extended.
> 
> Example: ./build/tests/kms_flip -e --r flip-vs-modeset-vs-hang
> 
> v2, v3:
> * Fix the typo in args handler (Petri)
> v4:
> * Refactor to run on first & last pipes.

Looks Good to me.
Reviewed-by: Uma Shankar <uma.shankar@intel.com>

> Cc: Uma Shankar <uma.shankar@intel.com>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Karthik B S <karthik.b.s@intel.com>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
>  tests/kms_flip.c | 30 +++++++++++++++++++++++++++++-
>  1 file changed, 29 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/kms_flip.c b/tests/kms_flip.c index 8f736652be..631eba9876
> 100755
> --- a/tests/kms_flip.c
> +++ b/tests/kms_flip.c
> @@ -85,6 +85,8 @@
>  #define DRM_CAP_TIMESTAMP_MONOTONIC 6
>  #endif
> 
> +static bool all_pipes = false;
> +
>  drmModeRes *resources;
>  int drm_fd;
>  static struct buf_ops *bops;
> @@ -1450,6 +1452,11 @@ static int run_test(int duration, int flags)
>  	/* Count output configurations to scale test runtime. */
>  	for (i = 0; i < resources->count_connectors; i++) {
>  		for (n = 0; n < resources->count_crtcs; n++) {
> +			/* Limit the execution to 2 CRTCs (first & last) for hang tests
> */
> +			if ((flags & TEST_HANG) && !all_pipes &&
> +			    n != 0 && n != (resources->count_crtcs - 1))
> +				continue;
> +
>  			memset(&o, 0, sizeof(o));
>  			o.count = 1;
>  			o._connector[0] = resources->connectors[i]; @@ -1474,6
> +1481,11 @@ static int run_test(int duration, int flags)
>  		for (n = 0; n < resources->count_crtcs; n++) {
>  			int crtc_idx;
> 
> +			/* Limit the execution to 2 CRTCs (first & last) for hang tests
> */
> +			if ((flags & TEST_HANG) && !all_pipes &&
> +			    n != 0 && n != (resources->count_crtcs - 1))
> +				continue;
> +
>  			memset(&o, 0, sizeof(o));
>  			o.count = 1;
>  			o._connector[0] = resources->connectors[i]; @@ -1604,7
> +1616,23 @@ static void test_nonblocking_read(int in)
>  	close(fd);
>  }
> 
> -igt_main
> +static int opt_handler(int opt, int opt_index, void *data) {
> +	switch (opt) {
> +		case 'e':
> +			all_pipes = true;
> +			break;
> +		default:
> +			return IGT_OPT_HANDLER_ERROR;
> +	}
> +
> +	return IGT_OPT_HANDLER_SUCCESS;
> +}
> +
> +const char *help_str =
> +	"  -e \tRun on all pipes. (By default subtests will run on two
> +pipes)\n";
> +
> +igt_main_args("e", NULL, help_str, opt_handler, NULL)
>  {
>  	struct {
>  		int duration;
> --
> 2.20.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2021-07-23  5:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 12:56 [igt-dev] [PATCH i-g-t 0/3] Limit the HANG tests to two pipes Bhanuprakash Modem
2021-07-05  5:42 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-07-05  6:51 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-05 12:56 ` [igt-dev] [PATCH i-g-t 1/3] tests/kms_busy: Limit the execution " Bhanuprakash Modem
2021-07-23  5:23   ` Shankar, Uma
2021-07-05 12:56 ` [igt-dev] [PATCH i-g-t 2/3] tests/kms_flip: Restrict the hang tests " Bhanuprakash Modem
2021-07-23  5:34   ` Shankar, Uma [this message]
2021-07-05 12:56 ` [igt-dev] [PATCH i-g-t 3/3] tests/intel-ci: Remove hang tests from pre-merge blacklist Bhanuprakash Modem
2021-07-26  4:42   ` Karthik B S
2021-07-26  5:45   ` [igt-dev] [i-g-t V2 " Bhanuprakash Modem
2021-07-23  6:27 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the HANG tests to two pipes (rev2) Patchwork
2021-07-23 10:05 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-23 12:08   ` Modem, Bhanuprakash
2021-07-23 15:55     ` Vudum, Lakshminarayana
2021-07-23 15:35 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
2021-07-26  6:24 ` [igt-dev] ✓ Fi.CI.BAT: success for Limit the HANG tests to two pipes (rev3) Patchwork
2021-07-26  7:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=be36f63b32a447d6a8cf39e123771764@intel.com \
    --to=uma.shankar@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@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