From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: John Harrison <john.c.harrison@intel.com>,
Matthew Brost <matthew.brost@intel.com>,
igt-dev@lists.freedesktop.org
Cc: daniele.ceraolospurio@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t 3/3] i915/sysfs_preempt_timeout: Update test to work with GuC submission
Date: Fri, 17 Sep 2021 08:36:19 +0100 [thread overview]
Message-ID: <eb7fe459-226d-6426-e6f8-99e09637866a@linux.intel.com> (raw)
In-Reply-To: <900219d9-5e70-faa1-bb25-7f01c2d14738@intel.com>
On 16/09/2021 21:49, John Harrison wrote:
> On 9/16/2021 11:03, Matthew Brost wrote:
>> 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 preemption timeout 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. We don't run this section on any gen12+ platforms as we
>> assume GuC submission on these platforms.
Tigerlake as well or not care about removing the coverage from it?
Regards,
Tvrtko
>>
>> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
>
>> ---
>> tests/i915/sysfs_preempt_timeout.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/i915/sysfs_preempt_timeout.c
>> b/tests/i915/sysfs_preempt_timeout.c
>> index d176ae72e..fe6b30236 100644
>> --- a/tests/i915/sysfs_preempt_timeout.c
>> +++ b/tests/i915/sysfs_preempt_timeout.c
>> @@ -29,6 +29,7 @@
>> #include <sys/types.h>
>> #include <unistd.h>
>> +#include "igt.h"
>> #include "igt_params.h"
>> #include "drmtest.h"
>> #include "i915/gem.h"
>> @@ -41,7 +42,7 @@
>> #include "sw_sync.h"
>> #define ATTR "preempt_timeout_ms"
>> -#define RESET_TIMEOUT 50 /* milliseconds, at least one jiffie for
>> kworker */
>> +#define RESET_TIMEOUT 1000 /* milliseconds, at long enough for an
>> error capture */
>> static bool __enable_hangcheck(int dir, bool state)
>> {
>> @@ -254,6 +255,9 @@ static void test_off(int i915, int engine)
>> gem_quiescent_gpu(i915);
>> igt_require(enable_hangcheck(i915, false));
>> + /* Not a supported behavior for GuC enabled platforms */
>> + igt_require(intel_gen(intel_get_drm_devid(i915)) < 12);
>> +
>> igt_assert(igt_sysfs_scanf(engine, "class", "%u", &class) == 1);
>> igt_assert(igt_sysfs_scanf(engine, "instance", "%u", &inst) == 1);
>
next prev parent reply other threads:[~2021-09-17 7:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 18:02 [igt-dev] [PATCH i-g-t 0/3] IGT fixes for priority management + preempt timeout with GuC submission Matthew Brost
2021-09-16 18:02 ` [igt-dev] [PATCH i-g-t 1/3] i915/gem_exec_schedule: Make gem_exec_schedule understand static priority mapping Matthew Brost
2021-10-04 23:24 ` Daniele Ceraolo Spurio
2021-09-16 18:03 ` [igt-dev] [PATCH i-g-t 2/3] i915/gem_ctx_shared: Make gem_ctx_shared " Matthew Brost
2021-10-04 23:26 ` Daniele Ceraolo Spurio
2021-10-05 10:44 ` Tvrtko Ursulin
2021-10-05 16:44 ` Matthew Brost
2021-10-06 8:12 ` Tvrtko Ursulin
2021-10-06 16:41 ` Matthew Brost
2021-10-06 18:34 ` Tvrtko Ursulin
2021-10-08 17:49 ` Matthew Brost
2021-10-11 8:04 ` Tvrtko Ursulin
2021-10-11 17:18 ` Matthew Brost
2021-10-11 18:50 ` John Harrison
2021-10-12 8:02 ` Tvrtko Ursulin
2021-10-12 17:20 ` Matthew Brost
2021-10-13 14:13 ` Tvrtko Ursulin
2021-09-16 18:03 ` [igt-dev] [PATCH i-g-t 3/3] i915/sysfs_preempt_timeout: Update test to work with GuC submission Matthew Brost
2021-09-16 20:49 ` John Harrison
2021-09-17 7:36 ` Tvrtko Ursulin [this message]
2021-09-17 16:14 ` Matthew Brost
2021-09-20 9:22 ` Tvrtko Ursulin
2021-09-16 19:33 ` [igt-dev] ✓ Fi.CI.BAT: success for IGT fixes for priority management + preempt timeout " Patchwork
2021-09-16 22:07 ` [igt-dev] ✗ Fi.CI.IGT: 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=eb7fe459-226d-6426-e6f8-99e09637866a@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=matthew.brost@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