intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Allow userspace to request no-error-capture upon GPU hangs
Date: Wed, 16 Dec 2015 17:30:18 +0000	[thread overview]
Message-ID: <56719FAA.1080209@intel.com> (raw)
In-Reply-To: <20151216100914.GT30437@phenom.ffwll.local>

On 16/12/15 10:09, Daniel Vetter wrote:
> On Wed, Dec 16, 2015 at 10:00:44AM +0000, Chris Wilson wrote:
>> On Wed, Dec 16, 2015 at 09:54:47AM +0100, Daniel Vetter wrote:
>>> On Fri, Dec 11, 2015 at 10:18:35PM +0000, Chris Wilson wrote:
>>>> igt likes to inject GPU hangs into its command streams. However, as we
>>>> expect these hangs, we don't actually want them recorded in the dmesg
>>>> output or stored in the i915_error_state (usually). To accomodate this
>>>> allow userspace to set a flag on the context that any hang emanating
>>>> from that context will not be recorded. We still do the error capture
>>>> (otherwise how do we find the guilty context and know its intent?) as
>>>> part of the reason for random GPU hang injection is to exercise the race
>>>> conditions between the error capture and normal execution.
>>>>
>>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>>
>>> Hm, I do like that we exercise the full paths all the time, increasing
>>> chances for fireworks. What's the motivation here? Is there some
>>> substantial speed-up?
>>
>> No, since we keep doing the error-capture (we have to, we haven't fixed
>> the bugs in it yet!), the only benefits are:
>>
>> (a) Reduce dmesg spam during igt
>> (b) simulating hangs doesn't leave an error-state around, or rather, we
>> don't leave the simulated error state and igt doesn't eat a *genuine* hang
>> that occurred during or before the test.
>
> Oh, should better wait for coffee to kick in - I didn't realize that all
> that code still runs, and the only thing that changes is whether we'll
> store the capture error state in the global slot used by debugfs.
>
> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Note this is the first version, obsoleted by the one Chris posted 41 
minutes later, and which I already gave an R-B, with qualifications:

http://www.spinics.net/lists/intel-gfx/msg83235.html

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

      reply	other threads:[~2015-12-16 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 22:18 [PATCH] drm/i915: Allow userspace to request no-error-capture upon GPU hangs Chris Wilson
2015-12-16  8:54 ` Daniel Vetter
2015-12-16 10:00   ` Chris Wilson
2015-12-16 10:09     ` Daniel Vetter
2015-12-16 17:30       ` Dave Gordon [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=56719FAA.1080209@intel.com \
    --to=david.s.gordon@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;
as well as URLs for NNTP newsgroup(s).