Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: pallavi.mishra@intel.com
To: igt-dev@lists.freedesktop.org, kamil.konieczny@intel.com
Subject: [igt-dev] [PATCH i-g-t 0/2] Increase timeout for GuC submission
Date: Wed, 29 Mar 2023 10:58:46 +0530	[thread overview]
Message-ID: <20230329052848.1076928-1-pallavi.mishra@intel.com> (raw)

From: Pallavi Mishra <pallavi.mishra@intel.com>

Increase reset timeout as resets can take a bit longer with GuC
submission because an error capture is done and with a large GuC log (16
MB) these take a while.

Don't run 'off' section as with GuC submission we don't handle
dynamically changing the timeslice duration from 'off' to 'on' on a
currently running context. This is not bug in GuC submission rather an
architectural decision to not implement this as there is no user aside
from IGTs.

Pallavi Mishra (2):
  [igt-dev][PATCH i-g-t] tests/i915: Increase timeout for GuC submission
  [igt-dev][PATCH i-g-t] i915/sysfs_timeslice_duration: skip off subtest
    for GuC submission

 tests/i915/sysfs_heartbeat_interval.c |  2 +-
 tests/i915/sysfs_timeslice_duration.c | 10 +++++++++-
 2 files changed, 10 insertions(+), 2 deletions(-)

-- 
2.25.1

             reply	other threads:[~2023-03-29  5:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  5:28 pallavi.mishra [this message]
2023-03-29  5:28 ` [igt-dev] [PATCH 1/2] [PATCH i-g-t] tests/i915: Increase timeout for GuC submission pallavi.mishra
2023-03-29  9:40   ` Kamil Konieczny
2023-03-29  5:28 ` [igt-dev] [PATCH 2/2] [PATCH i-g-t] i915/sysfs_timeslice_duration: skip off subtest " pallavi.mishra
2023-03-29  9:46   ` Kamil Konieczny
2023-03-29  6:05 ` [igt-dev] ✓ Fi.CI.BAT: success for Increase timeout " Patchwork
2023-03-29 17:00 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20230329052848.1076928-1-pallavi.mishra@intel.com \
    --to=pallavi.mishra@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@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