From: Carlos Santa <carlos.santa@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v2] tests/gem_watchdog: GPU engine reset
Date: Fri, 5 Oct 2018 18:05:24 -0700 [thread overview]
Message-ID: <1538787925-144920-1-git-send-email-carlos.santa@intel.com> (raw)
This IGT test complements the Gen8+ engine-reset feature patch
series aka Timeout Detection and Recovery (TDR) that Michel Thierry
submitted here: https://patchwork.freedesktop.org/series/21868/, specifically
the Watchdog timer feature of the original that is still not in
upstream.
There are several pieces that are required in order to
get (TDR) Watchdog timer in upstream:
(1) having a proper IGT set of tests that can exercise the feature
(2) but more imporantly, having a qualified user space client such
as a media driver that can trigger the watchdog timer after submitting
GPU work that could reset the media engine after encountering a
hung engine for example.
This IGT test is to cover requirement (1) above.
Carlos Santa (1):
tests/gem_watchdog: Initial set of tests for GPU watchdog
tests/Makefile.sources | 1 +
tests/gem_watchdog.c | 186 +++++++++++++++++++++++++++++++++++++++++++++++++
tests/meson.build | 1 +
3 files changed, 188 insertions(+)
create mode 100644 tests/gem_watchdog.c
--
2.7.4
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2018-10-06 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 1:05 Carlos Santa [this message]
2018-10-06 1:05 ` [igt-dev] [PATCH i-g-t v2] tests/gem_watchdog: Initial set of tests for GPU watchdog Carlos Santa
2018-10-08 21:43 ` Antonio Argenziano
2018-10-09 8:27 ` Chris Wilson
2018-10-09 16:12 ` Antonio Argenziano
2018-10-06 2:39 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/gem_watchdog: Initial set of tests for GPU watchdog (rev2) Patchwork
2018-10-06 11:28 ` [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=1538787925-144920-1-git-send-email-carlos.santa@intel.com \
--to=carlos.santa@intel.com \
--cc=igt-dev@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