From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Drop forcewake w/a for missed interrupts/seqno on Sandybridge
Date: Fri, 22 Nov 2013 12:46:40 -0800 [thread overview]
Message-ID: <20131122124640.03107b22@jbarnes-desktop> (raw)
In-Reply-To: <1385152524-3130-1-git-send-email-chris@chris-wilson.co.uk>
On Fri, 22 Nov 2013 20:35:24 +0000
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> I believe, and an evening of i-g-t, that our original workaround for the
> missed interrupts on Sandybridge, that of holding forcewake whilst we
> wait for an interrupts, is no longer required. This leaves us dependent
> on the second workaround of forcing an UC read of the ACTHD before
> reading back the seqno from the snooped HWS. Dropping the forcewake
> should allow us to conserve a little power, not much as the GPU is meant
> to be busy whilst we wait for it!
>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/intel_ringbuffer.c | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> index 80893af4062b..6b121ba9d3f7 100644
> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> @@ -1030,11 +1030,6 @@ gen6_ring_get_irq(struct intel_ring_buffer *ring)
> if (!dev->irq_enabled)
> return false;
>
> - /* It looks like we need to prevent the gt from suspending while waiting
> - * for an notifiy irq, otherwise irqs seem to get lost on at least the
> - * blt/bsd rings on ivb. */
> - gen6_gt_force_wake_get(dev_priv);
> -
> spin_lock_irqsave(&dev_priv->irq_lock, flags);
> if (ring->irq_refcount++ == 0) {
> if (HAS_L3_DPF(dev) && ring->id == RCS)
> @@ -1066,8 +1061,6 @@ gen6_ring_put_irq(struct intel_ring_buffer *ring)
> ilk_disable_gt_irq(dev_priv, ring->irq_enable_mask);
> }
> spin_unlock_irqrestore(&dev_priv->irq_lock, flags);
> -
> - gen6_gt_force_wake_put(dev_priv);
> }
>
> static bool
Yay! This is just what I was testing on BYT today, and it works there
too (and gives me tons more RC6 residency).
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-11-22 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 20:35 [PATCH] drm/i915: Drop forcewake w/a for missed interrupts/seqno on Sandybridge Chris Wilson
2013-11-22 20:46 ` Jesse Barnes [this message]
2013-11-26 9:29 ` 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=20131122124640.03107b22@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=chris@chris-wilson.co.uk \
--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