public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v2] tests/intel/kms_busy: Verify display reset happened
Date: Mon, 13 Apr 2026 12:43:54 +0300	[thread overview]
Message-ID: <276919d225ea11ee5187f581c3078520a80dcbfe@intel.com> (raw)
In-Reply-To: <20260413084545.2491-1-ville.syrjala@linux.intel.com>

On Mon, 13 Apr 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Use the new "intel_display_reset_count" debugfs file to confirm that the
> kernel did in fact perform the display reset.
>
> v2: Give the file an "intel_" namespace (Jani)
>     Don't leak the debugfs dirfd
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Seems reasonable.

Reviewed-by: Jani Nikula <jani.nikula@intel.com>


> ---
>  tests/intel/kms_busy.c | 23 +++++++++++++++++++++--
>  1 file changed, 21 insertions(+), 2 deletions(-)
>
> diff --git a/tests/intel/kms_busy.c b/tests/intel/kms_busy.c
> index e82380276666..039cc6ae8dab 100644
> --- a/tests/intel/kms_busy.c
> +++ b/tests/intel/kms_busy.c
> @@ -35,6 +35,7 @@
>  
>  #include "i915/gem.h"
>  #include "igt.h"
> +#include "igt_sysfs.h"
>  
>  /**
>   * SUBTEST: basic
> @@ -413,6 +414,18 @@ static void gpu_engines_restore_timeouts(int fd, int num_engines, const struct g
>  		gem_engine_properties_restore(fd, &props[i]);
>  }
>  
> +static uint32_t display_reset_count(int drm_fd)
> +{
> +	uint32_t count;
> +	int dir;
> +
> +	dir = igt_debugfs_dir(drm_fd);
> +	count = igt_sysfs_get_u32(dir, "intel_display_reset_count");
> +	close(dir);
> +
> +	return count;
> +}
> +
>  const char *help_str =
>  	"  -e \tRun on all pipes. (By default subtests will run on two pipes)\n";
>  
> @@ -549,16 +562,22 @@ int igt_main_args("e", NULL, help_str, opt_handler, NULL)
>  					continue;
>  
>  				igt_dynamic_f("pipe-%s", igt_crtc_name(crtc)) {
> -					if (tests[i].reset)
> +					uint32_t reset_count_pre = 0;
> +
> +					if (tests[i].reset) {
>  						igt_set_module_param_int(display.drm_fd, "force_reset_modeset_test", 1);
> +						reset_count_pre = display_reset_count(display.drm_fd);
> +					}
>  
>  					test_hang(&display,
>  						  crtc,
>  						  output,
>  						  tests[i].modeset, tests[i].hang_newfb);
>  
> -					if (tests[i].reset)
> +					if (tests[i].reset) {
>  						igt_set_module_param_int(display.drm_fd, "force_reset_modeset_test", 0);
> +						igt_assert_neq(reset_count_pre, display_reset_count(display.drm_fd));
> +					}
>  				}
>  			}

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-04-13  9:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09 20:09 [PATCH i-g-t] tests/intel/kms_busy: Verify display reset happened Ville Syrjala
2026-04-10  3:34 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-04-10  3:50 ` ✓ i915.CI.BAT: " Patchwork
2026-04-10  8:37 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-10 23:27 ` ✗ i915.CI.Full: " Patchwork
2026-04-13  8:45 ` [PATCH i-g-t v2] " Ville Syrjala
2026-04-13  9:43   ` Jani Nikula [this message]
2026-04-13 23:16 ` ✓ i915.CI.BAT: success for tests/intel/kms_busy: Verify display reset happened (rev2) Patchwork
2026-04-13 23:21 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-14  1:19 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-14  5:03 ` ✗ i915.CI.Full: 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=276919d225ea11ee5187f581c3078520a80dcbfe@intel.com \
    --to=jani.nikula@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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