Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 4/4] tests/intel/xe_wedged: Test wedged_mode=1 after had toggled mode=2
Date: Wed, 24 Apr 2024 08:22:40 +0530	[thread overview]
Message-ID: <9513bcc4-3a90-411f-baba-de3c037e9b54@intel.com> (raw)
In-Reply-To: <20240423222220.1285742-4-rodrigo.vivi@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]


On 24-04-2024 03:52, Rodrigo Vivi wrote:
> Let's toggle between different modes.
>
> Suggested-by: Himal Prasad Ghimiray<himal.prasad.ghimiray@intel.com>
> Signed-off-by: Rodrigo Vivi<rodrigo.vivi@intel.com>
> ---
>   tests/intel/xe_wedged.c | 14 ++++++++++++++
>   1 file changed, 14 insertions(+)
>
> diff --git a/tests/intel/xe_wedged.c b/tests/intel/xe_wedged.c
> index 35fc905e7..b9bd49fad 100644
> --- a/tests/intel/xe_wedged.c
> +++ b/tests/intel/xe_wedged.c
> @@ -216,6 +216,10 @@ simple_hang(int fd)
>    * SUBTEST: wedged-at-any-timeout
>    * Description: Force Xe device wedged after a simple guc timeout
>    */
> +/**
> + * SUBTEST: wedged-mode-toggle
> + * Description: Test wedged.mode=1 after testing wedged.mode=2
> + */
>   igt_main
>   {
>   	struct drm_xe_engine_class_instance *hwe;
> @@ -257,6 +261,16 @@ igt_main
>   			simple_exec(fd, hwe);
>   	}
>   
> +	igt_subtest_f("wedged-mode-toggle") {
> +		igt_require(igt_debugfs_exists(fd, "wedged_mode", O_RDWR));
> +
> +		igt_debugfs_write(fd, "wedged_mode", "2");
> +		igt_assert_eq(simple_ioctl(fd), 0);
> +		igt_debugfs_write(fd, "wedged_mode", "1");
> +		simple_hang(fd);
> +		igt_assert_eq(simple_ioctl(fd), 0);
> +	}
> +


LGTM.

Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>

>   	igt_fixture {
>   		if (igt_debugfs_exists(fd, "fail_gt_reset/probability", O_RDWR)) {
>   			igt_debugfs_write(fd, "fail_gt_reset/probability", "0");

[-- Attachment #2: Type: text/html, Size: 2489 bytes --]

  reply	other threads:[~2024-04-24  2:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 22:22 [PATCH i-g-t 1/4] tests/intel/xe_wedged: Introduce a new test for Xe device wedged state Rodrigo Vivi
2024-04-23 22:22 ` [PATCH i-g-t 2/4] tests/intel/xe_wedged: Also add a simple exec to confirm GPU health Rodrigo Vivi
2024-04-23 22:22 ` [PATCH i-g-t 3/4] tests/intel/xe_wedged: Introduce test for wedged_mode=2 Rodrigo Vivi
2024-04-23 22:22 ` [PATCH i-g-t 4/4] tests/intel/xe_wedged: Test wedged_mode=1 after had toggled mode=2 Rodrigo Vivi
2024-04-24  2:52   ` Ghimiray, Himal Prasad [this message]
2024-04-24  0:24 ` ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/4] tests/intel/xe_wedged: Introduce a new test for Xe device wedged state Patchwork
2024-04-24 16:50   ` Kamil Konieczny
2024-04-24  1:09 ` ✓ CI.xeBAT: success " Patchwork
2024-04-24 14:35 ` ✗ CI.xeFULL: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-04-23 22:20 [PATCH i-g-t 1/4] " Rodrigo Vivi
2024-04-23 22:20 ` [PATCH i-g-t 4/4] tests/intel/xe_wedged: Test wedged_mode=1 after had toggled mode=2 Rodrigo Vivi

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=9513bcc4-3a90-411f-baba-de3c037e9b54@intel.com \
    --to=himal.prasad.ghimiray@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=rodrigo.vivi@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