From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/selftests: Add a safety net to live_workarounds
Date: Wed, 11 Jul 2018 12:39:14 +0100 [thread overview]
Message-ID: <153130914444.18500.2234057696448611929@skylake-alporthouse-com> (raw)
In-Reply-To: <87muuyrozu.fsf@gaia.fi.intel.com>
Quoting Mika Kuoppala (2018-07-11 12:27:49)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > Since live_workarounds poke around the w/a registers and checks to see
> > if they survive across a reset, we are prone to fouling the machine and
> > leaving it in a non-recoverable state. Wrap the probe inside a timeout
> > to abort the test if the reset fails.
> >
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107188
>
> How can we tell it is not about just reset flakyness but
> associated whitelist poking?
By reading the dmesg. All we are doing here is breaking the indefinite
wait (as we've disabled hangcheck so as to not interfere with out own
resets) before owatch declares INCOMPLETE.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-11 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 9:59 [PATCH] drm/i915/selftests: Add a safety net to live_workarounds Chris Wilson
2018-07-11 10:39 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-07-11 10:58 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-11 11:27 ` [PATCH] " Mika Kuoppala
2018-07-11 11:39 ` Chris Wilson [this message]
2018-07-11 12:27 ` [PATCH v2] " Chris Wilson
2018-07-11 12:29 ` [PATCH v3] " Chris Wilson
2018-07-11 13:05 ` Mika Kuoppala
2018-07-11 13:19 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Add a safety net to live_workarounds (rev3) Patchwork
2018-07-11 13:35 ` ✓ Fi.CI.BAT: success " 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=153130914444.18500.2234057696448611929@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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 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.