From: Carlos Santa <carlos.santa@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [RFC] IGT GPU watchdog
Date: Mon, 15 Apr 2019 11:22:50 -0700 [thread overview]
Message-ID: <20190415182251.22427-1-carlos.santa@intel.com> (raw)
Sharing this at this point as RFC to help expand the coverage
on this topic and help me debug some of the issues I am seeing.
The latest patch series in the kernel: https://patchwork.kernel.org/patch/10866659/
Test Coverage:
1. gem context created with a long batch run until completion
2. gem context created with a long batch but canceled after some time
using gpu watchdog timeout
3. 2 gem contexts created, ctx2 executed and ctx1 canceled after some
time using gpu watchdog timeout
4. the inverse of #3 above, ctx2 canceled after some time using gpu
watchdog time and ctx1 run until completion.
Preemption handling
1. Submit a long batch and after half of the executed run time
submit a higher priority batch with half the duration. Very the
latter was executed.
2. Submit a low priority long batch without gpu watchdog then
a higher priority with gpu watchdog and verify whether the
higher priority batch was canceled before the low priority
one completed.
Known issues:
1. The fence status EIO is not getting propagated in the kernel layer
after an engine reset using gpu watchdog, after each reset the fence
still returns -1.
2. The creation of a gem context with a low or high priority value
doesn't seem to work correctly, need help on this to test preemption,
see the code below as reference.
3. TODO: the subtest "gpu-watchdog-long-batch-2-contexts" uses a dummy
sleep(6) for now but this needs to be changed. The contexts can't be
destroyed either until both threads are done executing, so commented out
for now.
Carlos Santa (1):
tests/gem_watchdog: Initial set of tests for GPU watchdog
tests/Makefile.sources | 3 +
tests/i915/gem_watchdog.c | 439 ++++++++++++++++++++++++++++++++++++++++++++++
tests/meson.build | 1 +
3 files changed, 443 insertions(+)
create mode 100644 tests/i915/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:[~2019-04-15 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 18:22 Carlos Santa [this message]
2019-04-15 18:22 ` [igt-dev] [RFC] tests/gem_watchdog: Initial set of tests for GPU watchdog Carlos Santa
2019-04-15 21:50 ` Antonio Argenziano
2019-04-16 2:02 ` Carlos Santa
2019-04-16 20:16 ` Antonio Argenziano
2019-04-16 20:21 ` Chris Wilson
2019-04-16 20:29 ` Antonio Argenziano
2019-04-15 18:32 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/gem_watchdog: Initial set of tests for GPU watchdog (rev3) 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=20190415182251.22427-1-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