Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Krishnaiah Bommu <krishnaiah.bommu@intel.com>
Subject: Re: [igt-dev] [PATCH] i915/gem_eio: increasing the timeout for forced reset completion
Date: Thu, 14 Apr 2022 15:01:10 +0200	[thread overview]
Message-ID: <YlgbFo7V3xQ95Wxt@kamilkon-DESK1> (raw)
In-Reply-To: <20220414102304.1745-1-krishnaiah.bommu@intel.com>

Dnia 2022-04-14 at 15:53:04 +0530, krishnaiah.bommu@intel.com napisał(a):
> From: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
> 
> GUC log capture is taking more time on few platforms, so increasing the timeout
> 
> Signed-off-by: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
> Cc: Konieczny Kamil <kamil.konieczny@intel.com>
-------------------------------------- ^
Please use my @linux.intel.com address.

> Cc: John Harrison <john.c.harrison@intel.com>
> Cc: Andi Shyti <andi.shyti@intel.com>
> ---
>  tests/i915/gem_eio.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/i915/gem_eio.c b/tests/i915/gem_eio.c
> index d9689534d5a..94c3bc04644 100644
> --- a/tests/i915/gem_eio.c
> +++ b/tests/i915/gem_eio.c
> @@ -72,8 +72,11 @@ static void trigger_reset(int fd)
>  	igt_kmsg(KMSG_DEBUG "Forcing GPU reset\n");
>  	igt_force_gpu_reset(fd);
>  
> -	/* The forced reset should be immediate */
> -	igt_assert_lte(igt_seconds_elapsed(&ts), 2);
> +	/* The forced reset should be immediate, even though
> +	 * GUC log capture is taking more time on few platforms,
> +	 * so Increasing the timeout
> +	 */
> +	igt_assert_lte(igt_seconds_elapsed(&ts), 10);

Please use new timeout variable and make it 10 only for GuC
submissions, you can use:

bool gem_using_guc_submission(int fd);

from lib/i915/gem_submission.h

Later in the same function 10 is also used so imho we should
make this number lower, like 7 or increase that second one.

>  
>  	/* And just check the gpu is indeed running again */
>  	igt_kmsg(KMSG_DEBUG "Checking that the GPU recovered\n");
> -- 
> 2.25.1
>
Regards,
Kamil
 

  parent reply	other threads:[~2022-04-14 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 10:23 [igt-dev] [PATCH] i915/gem_eio: increasing the timeout for forced reset completion krishnaiah.bommu
2022-04-14 11:38 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-04-14 13:01 ` Kamil Konieczny [this message]
2022-04-14 13:38 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2022-04-18  5:04 [igt-dev] [PATCH] " krishnaiah.bommu
2022-04-18  5:29 ` Dixit, Ashutosh
2022-04-20  9:52 ` Kamil Konieczny

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=YlgbFo7V3xQ95Wxt@kamilkon-DESK1 \
    --to=kamil.konieczny@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=krishnaiah.bommu@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