From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
intel-gfx@lists.freedesktop.org, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] tests/gem_ctx_persistence: Skip hang subtest with GuC
Date: Wed, 7 Jun 2023 15:47:41 +0200 [thread overview]
Message-ID: <34309cb8-d6e5-7842-52ad-369960440fb6@intel.com> (raw)
In-Reply-To: <20230606221418.296888-1-vinay.belgaumkar@intel.com>
On 07.06.2023 00:14, Vinay Belgaumkar wrote:
> Hang subtest is not supported with GuC submission enabled >
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Maybe providing more specific explanation would be better. Sth like:
GuC does not support dynamically configurable options, particularly
hangcheck disabling/enabling.
This is at least what I understood from internal bug tracker.
I wonder if it shouldn't be done also on driver level.
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
Regards
Andrzej
> ---
> tests/i915/gem_ctx_persistence.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/i915/gem_ctx_persistence.c b/tests/i915/gem_ctx_persistence.c
> index df9b1c491..d2558354e 100644
> --- a/tests/i915/gem_ctx_persistence.c
> +++ b/tests/i915/gem_ctx_persistence.c
> @@ -577,6 +577,8 @@ static void test_nohangcheck_hang(int i915, const intel_ctx_cfg_t *cfg)
> int testable_engines = 0;
> int dir;
>
> + igt_require(!gem_using_guc_submission(i915));
> +
> cleanup(i915);
>
> /*
next prev parent reply other threads:[~2023-06-07 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 22:14 [igt-dev] [PATCH i-g-t] tests/gem_ctx_persistence: Skip hang subtest with GuC Vinay Belgaumkar
2023-06-06 23:20 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-07 13:47 ` Andrzej Hajda [this message]
2023-06-07 15:00 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-06-07 17:29 ` [igt-dev] [Intel-gfx] [PATCH i-g-t] " 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=34309cb8-d6e5-7842-52ad-369960440fb6@intel.com \
--to=andrzej.hajda@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vinay.belgaumkar@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