From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: ville.syrjala@linux.intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Don't ban default context when stop_rings!=0
Date: Fri, 21 Feb 2014 17:52:32 +0200 [thread overview]
Message-ID: <87ha7sihtr.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <1392992807-25806-1-git-send-email-ville.syrjala@linux.intel.com>
ville.syrjala@linux.intel.com writes:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> If we've explicitly stopped the rings for testing purposes, don't ban
> the default context. Fixes kms_flip hang tests.
>
To keep logs clean from 'unnecessary' hang messages we set stop_rings also on
all the gem_reset_stats hanging tests. I think this breaks all the ban
tests on gem_reset_stats.
So we have dig this nice hole, for avoiding dmesg output on cases
where dmesg output should be valid and justificed.
-Mika
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> I'm not sure this is what we want in general, but it's what kms_flip expects
> currently.
>
> drivers/gpu/drm/i915/i915_gem.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index 3618bb0..52f9ea7 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -2259,14 +2259,13 @@ static bool i915_context_is_banned(struct drm_i915_private *dev_priv,
> return true;
>
> if (elapsed <= DRM_I915_CTX_BAN_PERIOD) {
> - if (dev_priv->gpu_error.stop_rings == 0 &&
> - i915_gem_context_is_default(ctx)) {
> - DRM_ERROR("gpu hanging too fast, banning!\n");
> - } else {
> + if (!i915_gem_context_is_default(ctx)) {
> DRM_DEBUG("context hanging too fast, banning!\n");
> + return true;
> + } else if (dev_priv->gpu_error.stop_rings == 0) {
> + DRM_ERROR("gpu hanging too fast, banning!\n");
> + return true;
> }
> -
> - return true;
> }
>
> return false;
> --
> 1.8.3.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-02-21 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 14:26 [PATCH] drm/i915: Don't ban default context when stop_rings!=0 ville.syrjala
2014-02-21 15:52 ` Mika Kuoppala [this message]
2014-02-21 16:13 ` Mika Kuoppala
2014-03-05 13:03 ` Daniel Vetter
2014-02-21 16:30 ` Mika Kuoppala
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=87ha7sihtr.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox