All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH igt] lib: Force global reset + uevents for hang detector
Date: Mon, 05 Jun 2017 13:23:46 +0100	[thread overview]
Message-ID: <149666542654.14666.6729414702059234109@mail.alporthouse.com> (raw)
In-Reply-To: <87wp8qr8ho.fsf@gaia.fi.intel.com>

Quoting Mika Kuoppala (2017-06-05 12:15:15)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
> > +     /*
> > +      * Disable per-engine reset to force an error uevent. We don't
> > +      * expect to get any hangs whilst the detector is enabled (if we do
> > +      * they are a test failure!) and so the loss of per-engine reset
> > +      * functionality is not an issue.
> > +      */
> 
> Makes sense. Tho I only looked one test which disables
> hang detector before starting the more fine grained hang tests.

The alternative is that we send an error uevent for per-engine resets.
But I think that's overkill for TDR, and we want to keep as much as
possible generic. :|
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-06-05 12:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 11:05 [PATCH igt] lib: Force global reset + uevents for hang detector Chris Wilson
2017-06-05 11:15 ` Mika Kuoppala
2017-06-05 12:00   ` Chris Wilson
2017-06-05 12:23   ` Chris Wilson [this message]
2017-06-05 12:13 ` [PATCH igt v2] " Chris Wilson
2017-06-05 21:21   ` Michel Thierry
2017-06-05 22:57     ` Chris Wilson
2017-06-05 23:14       ` Michel Thierry

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=149666542654.14666.6729414702059234109@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@linux.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.