public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ben Widawsky <benjamin.widawsky@intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, miku@iki.fi
Subject: Re: [PATCH] drm/i915: Fix forcewake counts for gen8
Date: Tue, 18 Feb 2014 10:21:45 -0800	[thread overview]
Message-ID: <20140218182145.GA904@intel.com> (raw)
In-Reply-To: <1392743424-2039-1-git-send-email-mika.kuoppala@intel.com>

On Tue, Feb 18, 2014 at 07:10:24PM +0200, Mika Kuoppala wrote:
> Sometimes generic driver code gets forcewake explicitly by
> gen6_gt_force_wake_get(), which check forcewake_count before accessing
> hardware. However the register access with gen8_write function access
> low level hw accessors directly, ignoring the forcewake_count. This
> leads to nested forcewake get from hardware, in ring init and possibly
> elsewhere, causing forcewake ack clear errors and/or hangs.
> 
> Fix this by checking the forcewake count also in gen8_write
> 
> v2: Read side doesn't care about shadowed registers,
>     Remove __needs_put funkiness from gen8_write. (Ville)
>     Improved commit message.
> 
> References: https://bugs.freedesktop.org/show_bug.cgi?id=74007
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> Cc: Ben Widawsky <benjamin.widawsky@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>

Thanks for finding this. I'd been meaning to track down the extra "Timed
out" messages. I do wonder how this actually fixes a hang. Do you have
any idea?

Reviewed-by: Ben Widawsky <ben@bwidawsk.net>

> ---
>  drivers/gpu/drm/i915/intel_uncore.c |   19 ++++++++++---------
>  1 file changed, 10 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
> index c628414..d1e9d63 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -634,16 +634,17 @@ static bool is_gen8_shadowed(struct drm_i915_private *dev_priv, u32 reg)
>  #define __gen8_write(x) \
>  static void \
>  gen8_write##x(struct drm_i915_private *dev_priv, off_t reg, u##x val, bool trace) { \
> -	bool __needs_put = reg < 0x40000 && !is_gen8_shadowed(dev_priv, reg); \
>  	REG_WRITE_HEADER; \
> -	if (__needs_put) { \
> -		dev_priv->uncore.funcs.force_wake_get(dev_priv, \
> -							FORCEWAKE_ALL); \
> -	} \
> -	__raw_i915_write##x(dev_priv, reg, val); \
> -	if (__needs_put) { \
> -		dev_priv->uncore.funcs.force_wake_put(dev_priv, \
> -							FORCEWAKE_ALL); \
> +	if (reg < 0x40000 && !is_gen8_shadowed(dev_priv, reg)) { \
> +		if (dev_priv->uncore.forcewake_count == 0) \
> +			dev_priv->uncore.funcs.force_wake_get(dev_priv,	\
> +							      FORCEWAKE_ALL); \
> +		__raw_i915_write##x(dev_priv, reg, val); \
> +		if (dev_priv->uncore.forcewake_count == 0) \
> +			dev_priv->uncore.funcs.force_wake_put(dev_priv, \
> +							      FORCEWAKE_ALL); \
> +	} else { \
> +		__raw_i915_write##x(dev_priv, reg, val); \
>  	} \
>  	REG_WRITE_FOOTER; \
>  }
> -- 
> 1.7.9.5
> 

-- 
Ben Widawsky, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-02-18 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 15:48 [PATCH] drm/i915: fix forcewake counts for gen8 Mika Kuoppala
2014-02-18 16:42 ` Ville Syrjälä
2014-02-18 17:10   ` [PATCH] drm/i915: Fix " Mika Kuoppala
2014-02-18 18:21     ` Ben Widawsky [this message]
2014-02-18 19:08       ` 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=20140218182145.GA904@intel.com \
    --to=benjamin.widawsky@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@linux.intel.com \
    --cc=miku@iki.fi \
    /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