From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: Reinstate error level message for non-simulated gpu hangs
Date: Wed, 01 Oct 2014 17:40:49 +0300 [thread overview]
Message-ID: <87y4szsvim.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <1412164990-27013-1-git-send-email-daniel.vetter@ffwll.ch>
Daniel Vetter <daniel.vetter@ffwll.ch> writes:
> This seems to have been accidentally lost in
>
> commit be62acb4cce1389a28296852737e3917d9cc5b25
> Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Date: Fri Aug 30 16:19:28 2013 +0300
>
> drm/i915: ban badly behaving contexts
>
> Without this real gpu hangs only log output at info level, which gets
> filtered away by piglit's testrunner.
>
> v2: Tune down to notice level. Note that we need to add drm/i915 so
> that at least the automatic igt dmesg filtering still picks it up.
>
> v3: git add and lack of coffee don't mix well.
>
> v4: Message is in between hw and sw reset, so switch verb to
> continuous form.
>
> v5: Use i915_stop_rings_allow_warn for consistency. For Chris' case of
> injecting lots of hangs I guess we need to revamp this all anyway when
> merging. For now this should plug the regression for piglit testing
> mesa.
>
> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Kenneth Graunke <kenneth@whitecape.org>
> Reported-by: Kenneth Graunke <kenneth@whitecape.org>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index ea93ff151a74..fec4afe526c7 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -844,6 +844,9 @@ int i915_reset(struct drm_device *dev)
> }
> }
>
> + if (i915_stop_rings_allow_warn(dev_priv))
> + pr_notice("drm/i915: Resetting chip after gpu hang\n");
> +
I would have added also:
"As of now, further functionality or performance testing beyond this point is
utterly pointless."
Perhaps in caps.
-Mika
> if (ret) {
> DRM_ERROR("Failed to reset chip: %i\n", ret);
> mutex_unlock(&dev->struct_mutex);
> --
> 2.1.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-10-01 14:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 23:04 [PATCH] drm/i915: Reinstate error level message for non-simulated gpu hangs Daniel Vetter
2014-10-01 6:28 ` Chris Wilson
2014-10-01 8:13 ` Daniel Vetter
2014-10-01 8:19 ` Chris Wilson
2014-10-01 8:29 ` Daniel Vetter
2014-10-01 8:52 ` Kenneth Graunke
2014-10-01 9:10 ` Chris Wilson
2014-10-01 9:28 ` Daniel Vetter
2014-10-01 9:37 ` Chris Wilson
2014-10-01 9:41 ` Daniel Vetter
2014-10-01 9:50 ` Chris Wilson
2014-10-01 9:32 ` Daniel Vetter
2014-10-01 12:03 ` Daniel Vetter
2014-10-01 13:54 ` Chris Wilson
2014-10-01 14:40 ` Mika Kuoppala [this message]
[not found] <1412118259-4860-1-git-send-email-daniel.vetter@ffwll.c>
2014-10-01 9:15 ` Daniel Vetter
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=87y4szsvim.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@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