From: Daniel Vetter <daniel@ffwll.ch>
To: Arun Siluvery <arun.siluvery@linux.intel.com>
Cc: Intel-GFX@Lists.FreeDesktop.Org, Tomas Elf <tomas.elf@intel.com>
Subject: Re: [PATCH 10/20] drm/i915: Watchdog timeout: DRM kernel interface enablement
Date: Mon, 25 Jan 2016 16:58:03 +0100 [thread overview]
Message-ID: <20160125155803.GO11240@phenom.ffwll.local> (raw)
In-Reply-To: <56A237E0.3040908@linux.intel.com>
On Fri, Jan 22, 2016 at 02:08:32PM +0000, Arun Siluvery wrote:
> On 22/01/2016 13:59, Chris Wilson wrote:
> >On Fri, Oct 23, 2015 at 02:32:32AM +0100, Tomas Elf wrote:
> >>Final enablement patch for GPU hang recovery using watchdog timeout.
> >>Added execbuf flag for watchdog timeout in DRM kernel interface.
> >
> >Usual argument: per-batch or per-context flag? What's the use case being
> >consider that would favour one approach or another. That usecase should
> >be explained in the changelog so that we can be reminded of it again
> >later.
>
> It is per-batch, user expects certain workloads to be completed before
> watchdog times out hence it is per-batch.
> This is mainly used for media workloads, don't know the exact usecase but I
> guess encode/decode work of frame to complete within a short time etc. I
> will add these details to commit msg.
Usual reminder: We need an open-source user to get these new interfaces
in. Looking at that should make it pretty clear whether the watchdog
should be per-ctx or per-batch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-25 15:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 1:32 [PATCH 00/20] TDR/watchdog support for gen8 Tomas Elf
2015-10-23 1:32 ` [PATCH 01/20] drm/i915: Make i915_gem_reset_ring_status() public Tomas Elf
2015-10-23 1:32 ` [PATCH 02/20] drm/i915: Generalise common GPU engine reset request/unrequest code Tomas Elf
2015-10-23 1:32 ` [PATCH 03/20] drm/i915: TDR / per-engine hang recovery support for gen8 Tomas Elf
2015-10-23 1:32 ` [PATCH 04/20] drm/i915: TDR / per-engine hang detection Tomas Elf
2015-10-23 1:32 ` [PATCH 05/20] drm/i915: Extending i915_gem_check_wedge to check engine reset in progress Tomas Elf
2015-10-23 1:32 ` [PATCH 06/20] drm/i915: Reinstate hang recovery work queue Tomas Elf
2015-10-23 1:32 ` [PATCH 07/20] drm/i915: Watchdog timeout: Hang detection integration into error handler Tomas Elf
2015-10-23 1:32 ` [PATCH 08/20] drm/i915: Watchdog timeout: IRQ handler for gen8 Tomas Elf
2015-10-23 1:32 ` [PATCH 09/20] drm/i915: Watchdog timeout: Ringbuffer command emission " Tomas Elf
2015-10-23 1:32 ` [PATCH 10/20] drm/i915: Watchdog timeout: DRM kernel interface enablement Tomas Elf
2016-01-22 13:59 ` Chris Wilson
2016-01-22 14:08 ` Arun Siluvery
2016-01-25 15:58 ` Daniel Vetter [this message]
2015-10-23 1:32 ` [PATCH 11/20] drm/i915: Fake lost context event interrupts through forced CSB checking Tomas Elf
2015-10-23 1:32 ` [PATCH 12/20] drm/i915: Debugfs interface for per-engine hang recovery Tomas Elf
2015-10-23 1:32 ` [PATCH 13/20] drm/i915: Test infrastructure for context state inconsistency simulation Tomas Elf
2015-10-23 1:32 ` [PATCH 14/20] drm/i915: TDR/watchdog trace points Tomas Elf
2015-10-23 1:32 ` [PATCH 15/20] drm/i915: Port of Added scheduler support to __wait_request() calls Tomas Elf
2015-10-23 1:32 ` [PATCH 16/20] drm/i915: Fix __i915_wait_request() behaviour during hang detection Tomas Elf
2015-10-23 1:32 ` [PATCH 17/20] drm/i915: Extended error state with TDR count, watchdog count and engine reset count Tomas Elf
2015-10-23 1:32 ` [PATCH 18/20] drm/i915: TDR / per-engine hang recovery kernel docs Tomas Elf
2015-10-23 1:32 ` [PATCH 19/20] drm/i915: drm/i915 changes to simulated hangs Tomas Elf
2016-01-22 13:43 ` Chris Wilson
2016-01-22 13:52 ` Arun Siluvery
2015-10-23 1:32 ` [PATCH 20/20] drm/i915: Enable TDR / per-engine hang recovery Tomas Elf
-- strict thread matches above, loose matches on Subject: below --
2016-01-13 17:28 [PATCH 00/20] TDR/watchdog support for gen8 Arun Siluvery
2016-01-13 17:28 ` [PATCH 10/20] drm/i915: Watchdog timeout: DRM kernel interface enablement Arun Siluvery
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=20160125155803.GO11240@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=arun.siluvery@linux.intel.com \
--cc=tomas.elf@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.