From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/selftests: Mark live_forcewake_ops as unreliable
Date: Mon, 8 Apr 2019 10:24:08 -0700 [thread overview]
Message-ID: <fc42a77c-80ae-5327-3022-b569b05f1a6e@intel.com> (raw)
In-Reply-To: <20190407192649.14750-1-chris@chris-wilson.co.uk>
On 4/7/19 12:26 PM, Chris Wilson wrote:
> A couple of machines in the farm show quite frequent errors in the
> powerwells not being released. Either there is an external agent
> interferring with the powerwells, or the powerwell doesn't quite behave
> as we anticipate -- either way, the test is not reliable enough to be
> enabled by default in CI. It has served its immediate purpose in
> providing coverage as we made tweaks to forcewake, so keep it available
> for future testing.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110210
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
> ---
> drivers/gpu/drm/i915/selftests/intel_uncore.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/selftests/intel_uncore.c b/drivers/gpu/drm/i915/selftests/intel_uncore.c
> index ee0bc91f7664..86f9f44ac00f 100644
> --- a/drivers/gpu/drm/i915/selftests/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/selftests/intel_uncore.c
> @@ -155,6 +155,17 @@ static int live_forcewake_ops(void *arg)
> return 0;
> }
>
> + /*
> + * Not quite as reliable across the gen as one would hope.
> + *
> + * Either our theory of operation is incorrect, or there remain
> + * external parties interferring with the powerwells.
> + *
> + * https://bugs.freedesktop.org/show_bug.cgi?id=110210
> + */
> + if (!IS_ENABLED(CONFIG_DRM_I915_SELFTEST_BROKEN))
> + return 0;
> +
> /* We have to pick carefully to get the exact behaviour we need */
> for (r = registers; r->name; r++)
> if (r->platforms & INTEL_INFO(i915)->gen_mask)
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-08 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 19:19 [PATCH] drm/i915/selftests: Mark live_forcewake_ops as unreliable Chris Wilson
2019-04-07 19:26 ` Chris Wilson
2019-04-08 17:24 ` Daniele Ceraolo Spurio [this message]
2019-04-07 19:27 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-04-07 19:46 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-04-07 19:49 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Mark live_forcewake_ops as unreliable (rev2) Patchwork
2019-04-07 20:08 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-07 21:21 ` ✓ 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=fc42a77c-80ae-5327-3022-b569b05f1a6e@intel.com \
--to=daniele.ceraolospurio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).