All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Carlos Santa <carlos.santa@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: Gen8+ engine-reset
Date: Mon, 7 Jan 2019 10:11:34 +0000	[thread overview]
Message-ID: <2f8200ed-b3d1-bf31-77ab-9a37ffef2787@linux.intel.com> (raw)
In-Reply-To: <20190105024001.37629-1-carlos.santa@intel.com>


Hi,

We have had engine reset support in i915 for some time now. So lets call 
this work engine watchdog or something, just not engine reset.

By calling it engine reset we have confused sites like Phoronix and some 
our users.

Regards,

Tvrtko

On 05/01/2019 02:39, Carlos Santa wrote:
> 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.
> 
> The series was also successfully tested from userspace through the
> the Intel i965 media driver that is readily found on some
> Linux based OS including Ubuntu OS and as well as Chromium OS. 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 a 1 BSD ring.
> 
> Carlos Santa (1):
>    drm/i915: Only process VCS2 only when supported
> 
> Michel Thierry (7):
>    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: move emit_stop_watchdog until the very end of the
>      ring commands
>    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         |  17 +-
>   drivers/gpu/drm/i915/i915_reg.h         |   6 +
>   drivers/gpu/drm/i915/intel_hangcheck.c  |  20 ++-
>   drivers/gpu/drm/i915/intel_lrc.c        | 208 +++++++++++++++++++++++-
>   drivers/gpu/drm/i915/intel_ringbuffer.h |  10 ++
>   include/uapi/drm/i915_drm.h             |   7 +-
>   11 files changed, 428 insertions(+), 20 deletions(-)
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2019-01-07 10:11 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05  2:39 Gen8+ engine-reset Carlos Santa
2019-01-05  2:39 ` drm/i915: Add engine reset count in get-reset-stats ioctl Carlos Santa
2019-01-05  2:39 ` drm/i915: Watchdog timeout: IRQ handler for gen8+ Carlos Santa
2019-01-07 11:58   ` Tvrtko Ursulin
2019-01-07 12:16     ` Chris Wilson
2019-01-07 12:58       ` Tvrtko Ursulin
2019-01-07 13:02         ` Chris Wilson
2019-01-07 13:12           ` Tvrtko Ursulin
2019-01-07 13:43     ` Tvrtko Ursulin
2019-01-07 13:57       ` Chris Wilson
2019-01-07 16:58         ` Tvrtko Ursulin
2019-01-07 18:31           ` Chris Wilson
2019-01-11  0:47           ` Antonio Argenziano
2019-01-11  8:22             ` Tvrtko Ursulin
2019-01-11 17:31               ` Antonio Argenziano
2019-01-11 21:28                 ` John Harrison
2019-01-16 16:15                   ` Tvrtko Ursulin
2019-01-16 17:42                     ` Antonio Argenziano
2019-01-16 17:59                       ` Antonio Argenziano
2019-01-11  2:58           ` Carlos Santa
2019-01-24  0:13     ` Carlos Santa
2019-01-05  2:39 ` drm/i915: Watchdog timeout: Ringbuffer command emission " Carlos Santa
2019-01-07 12:21   ` Tvrtko Ursulin
2019-01-05  2:39 ` drm/i915: Watchdog timeout: DRM kernel interface to set the timeout Carlos Santa
2019-01-07 12:38   ` Tvrtko Ursulin
2019-01-07 12:50     ` Chris Wilson
2019-01-07 13:39       ` Tvrtko Ursulin
2019-01-07 13:51         ` Chris Wilson
2019-01-07 17:00     ` Tvrtko Ursulin
2019-01-07 17:20       ` Tvrtko Ursulin
2019-01-05  2:39 ` drm/i915: Watchdog timeout: Include threshold value in error state Carlos Santa
2019-01-05  4:19   ` kbuild test robot
2019-01-05  4:39   ` kbuild test robot
2019-01-05  2:39 ` drm/i915: Only process VCS2 only when supported Carlos Santa
2019-01-07 12:40   ` Tvrtko Ursulin
2019-01-24  0:20     ` Carlos Santa
2019-01-05  2:40 ` drm/i915/watchdog: move emit_stop_watchdog until the very end of the ring commands Carlos Santa
2019-01-07 12:50   ` Tvrtko Ursulin
2019-01-07 12:54     ` Chris Wilson
2019-01-07 13:01       ` Tvrtko Ursulin
2019-01-11  2:25     ` Carlos Santa
2019-01-05  2:40 ` drm/i915: Watchdog timeout: Blindly trust watchdog timeout for reset? Carlos Santa
2019-01-05  4:15   ` kbuild test robot
2019-01-05 13:32   ` kbuild test robot
2019-01-05  2:57 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-01-05  3:21 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-05  4:41 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-07 10:11 ` Tvrtko Ursulin [this message]

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=2f8200ed-b3d1-bf31-77ab-9a37ffef2787@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=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 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.