From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/selftests: Always use an active engine while resetting
Date: Fri, 15 Feb 2019 11:09:46 +0200 [thread overview]
Message-ID: <87mumxzacl.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190213224805.32021-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Currently, we only try to reset a live engine for checking the whitelist
> retention across a per-engine reset. For safety, it appears we need to
> prime the system with a hanging spinner before performing a full-device
> reset. (Figuring out the root cause behind the instability with handling
> a reset during a no-op request is a challenge for another test, the
> whitelist test has its own purpose.)
>
Agreed on the sentiment and it does what it says on the tin.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109626
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> .../drm/i915/selftests/intel_workarounds.c | 27 ++++++-------------
> 1 file changed, 8 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/selftests/intel_workarounds.c b/drivers/gpu/drm/i915/selftests/intel_workarounds.c
> index b15c4f26c593..d6bb2005024d 100644
> --- a/drivers/gpu/drm/i915/selftests/intel_workarounds.c
> +++ b/drivers/gpu/drm/i915/selftests/intel_workarounds.c
> @@ -237,14 +237,8 @@ switch_to_scratch_context(struct intel_engine_cs *engine,
> return PTR_ERR(ctx);
>
> rq = ERR_PTR(-ENODEV);
> - with_intel_runtime_pm(engine->i915, wakeref) {
> - if (spin)
> - rq = igt_spinner_create_request(spin,
> - ctx, engine,
> - MI_NOOP);
> - else
> - rq = i915_request_alloc(engine, ctx);
> - }
> + with_intel_runtime_pm(engine->i915, wakeref)
> + rq = igt_spinner_create_request(spin, ctx, engine, MI_NOOP);
>
> kernel_context_close(ctx);
>
> @@ -273,7 +267,6 @@ static int check_whitelist_across_reset(struct intel_engine_cs *engine,
> const char *name)
> {
> struct drm_i915_private *i915 = engine->i915;
> - bool want_spin = reset == do_engine_reset;
> struct i915_gem_context *ctx;
> struct igt_spinner spin;
> intel_wakeref_t wakeref;
> @@ -282,11 +275,9 @@ static int check_whitelist_across_reset(struct intel_engine_cs *engine,
> pr_info("Checking %d whitelisted registers (RING_NONPRIV) [%s]\n",
> engine->whitelist.count, name);
>
> - if (want_spin) {
> - err = igt_spinner_init(&spin, i915);
> - if (err)
> - return err;
> - }
> + err = igt_spinner_init(&spin, i915);
> + if (err)
> + return err;
>
> ctx = kernel_context(i915);
> if (IS_ERR(ctx))
> @@ -298,17 +289,15 @@ static int check_whitelist_across_reset(struct intel_engine_cs *engine,
> goto out;
> }
>
> - err = switch_to_scratch_context(engine, want_spin ? &spin : NULL);
> + err = switch_to_scratch_context(engine, &spin);
> if (err)
> goto out;
>
> with_intel_runtime_pm(i915, wakeref)
> err = reset(engine);
>
> - if (want_spin) {
> - igt_spinner_end(&spin);
> - igt_spinner_fini(&spin);
> - }
> + igt_spinner_end(&spin);
> + igt_spinner_fini(&spin);
>
> if (err) {
> pr_err("%s reset failed\n", name);
> --
> 2.20.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-02-15 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 22:48 [PATCH] drm/i915/selftests: Always use an active engine while resetting Chris Wilson
2019-02-14 15:53 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-02-14 22:02 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-02-15 9:09 ` Mika Kuoppala [this message]
2019-02-15 9:19 ` [PATCH] " Chris Wilson
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=87mumxzacl.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.