public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Carlos Santa <carlos.santa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v3 0/6] GEN8+ GPU Watchdog Reset Support
Date: Wed, 13 Feb 2019 18:57:07 -0800	[thread overview]
Message-ID: <20190214025713.34150-1-carlos.santa@intel.com> (raw)

This is a rebased on the original patch series from Michel Thierry
that can be found here:

https://patchwork.freedesktop.org/series/21868

Note that this series is only limited to the GPU Watchdog timeout
for execlists as it leaves out support
for GuC based submission for a later time.

PATCH v3 of this series was successfully tested from userspace
through an IGT test gem_watchdog --run-subtest basic-bsd1,
that test not in upstream yet.

Also, the changes on the i965 media userspace driver are currently
under review at

https://github.com/intel/intel-vaapi-driver/pull/429/files

The testbed used on this series included a SKL-based NUC with 
2 BSD rings as well as a KBL-based Chromebook with 1 BSD ring.

Michel Thierry (6):
  drm/i915: Add engine reset count in get-reset-stats ioctl
  drm/i915: Watchdog timeout: IRQ handler for gen8+
  drm/i915: Watchdog timeout: Ringbuffer command emission for gen8+
  drm/i915: Watchdog timeout: DRM kernel interface to set the timeout
  drm/i915: Watchdog timeout: Include threshold value in error state
  drm/i915: Watchdog timeout: Blindly trust watchdog timeout for reset?

 drivers/gpu/drm/i915/i915_drv.h         |  56 +++++++++
 drivers/gpu/drm/i915/i915_gem_context.c | 103 +++++++++++++++-
 drivers/gpu/drm/i915/i915_gem_context.h |   4 +
 drivers/gpu/drm/i915/i915_gpu_error.c   |  12 +-
 drivers/gpu/drm/i915/i915_gpu_error.h   |   5 +
 drivers/gpu/drm/i915/i915_irq.c         |  12 +-
 drivers/gpu/drm/i915/i915_reg.h         |   6 +
 drivers/gpu/drm/i915/intel_engine_cs.c  |   3 +
 drivers/gpu/drm/i915/intel_hangcheck.c  |  20 ++-
 drivers/gpu/drm/i915/intel_lrc.c        | 157 +++++++++++++++++++++++-
 drivers/gpu/drm/i915/intel_lrc.h        |   2 +
 drivers/gpu/drm/i915/intel_ringbuffer.h |  24 +++-
 include/uapi/drm/i915_drm.h             |   7 +-
 13 files changed, 390 insertions(+), 21 deletions(-)

-- 
2.17.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2019-02-14  2:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  2:57 Carlos Santa [this message]
2019-02-14  2:57 ` [PATCH v3 1/6] drm/i915: Add engine reset count in get-reset-stats ioctl Carlos Santa
2019-02-14  2:57 ` [PATCH v3 2/6] drm/i915: Watchdog timeout: IRQ handler for gen8+ Carlos Santa
2019-02-14  9:15   ` Chris Wilson
2019-02-14  2:57 ` [PATCH v3 3/6] drm/i915: Watchdog timeout: Ringbuffer command emission " Carlos Santa
2019-02-14  2:57 ` [PATCH v3 4/6] drm/i915: Watchdog timeout: DRM kernel interface to set the timeout Carlos Santa
2019-02-14  2:57 ` [PATCH v3 5/6] drm/i915: Watchdog timeout: Include threshold value in error state Carlos Santa
2019-02-14  2:57 ` [PATCH v3 6/6] drm/i915: Watchdog timeout: Blindly trust watchdog timeout for reset? Carlos Santa
2019-02-14 17:26 ` ✗ Fi.CI.BAT: failure for Gen8+ GPU Watchdog Reset Support (rev2) 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=20190214025713.34150-1-carlos.santa@intel.com \
    --to=carlos.santa@intel.com \
    --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