All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Graunke <kenneth@whitecape.org>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: apply HWSTAM writes to Ivy Bridge as well
Date: Fri, 01 Jul 2011 13:01:50 -0700	[thread overview]
Message-ID: <4E0E27AE.3040402@whitecape.org> (raw)
In-Reply-To: <1309543736-2335-1-git-send-email-jbarnes@virtuousgeek.org>

On 07/01/2011 11:08 AM, Jesse Barnes wrote:
> In an attempt to fix 38862 and 38863.
>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

Tested-by: Kenneth Graunke <kenneth@whitecape.org>

Prior to this patch, running the piglit test suite would randomly hang
the GPU unless I added msleeps between each test.  (Individual tests ran
fine.)

This patch fixes the issue.  I am now able to run piglit unmodified
without hanging the GPU.

Keith, could this go into -fixes?

Thanks for finding this, Chris and Jesse!

--Kenneth

> ---
>  drivers/gpu/drm/i915/i915_irq.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 2e18161..23d1ae6 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -1745,7 +1745,7 @@ static void ironlake_irq_preinstall(struct drm_device *dev)
>  		INIT_WORK(&dev_priv->rps_work, gen6_pm_rps_work);
>  
>  	I915_WRITE(HWSTAM, 0xeffe);
> -	if (IS_GEN6(dev)) {
> +	if (IS_GEN6(dev) || IS_GEN7(dev)) {
>  		/* Workaround stalls observed on Sandy Bridge GPUs by
>  		 * making the blitter command streamer generate a
>  		 * write to the Hardware Status Page for

  reply	other threads:[~2011-07-01 20:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 18:08 [PATCH] drm/i915: apply HWSTAM writes to Ivy Bridge as well Jesse Barnes
2011-07-01 20:01 ` Kenneth Graunke [this message]
2011-07-01 20:28   ` Keith Packard

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=4E0E27AE.3040402@whitecape.org \
    --to=kenneth@whitecape.org \
    --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 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.