All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 4/4] drm/i915: enable forcewake voodoo also for gen6
Date: Mon, 13 Feb 2012 11:00:05 +0100	[thread overview]
Message-ID: <20120213100005.GB5301@phenom.ffwll.local> (raw)
In-Reply-To: <d08817$33j9d0@azsmga001.ch.intel.com>

On Wed, Feb 08, 2012 at 10:00:54AM +0000, Chris Wilson wrote:
> On Wed, 25 Jan 2012 14:04:00 +0100, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > We still have reports of missed irqs even on Sandybridge with the
> > HWSTAM workaround in place. Testing by the bug reporter gets rid of
> > them with the forcewake voodoo and no HWSTAM writes.
> > 
> > Because I've slightly botched the rebasing I've left out the ACTHD
> > readback which is also required to get IVB working. Seems to still
> > work on the tester's machine, so I think we should go with the more
> > minmal approach on SNB. Especially since I've only found weak evidence
> > for holding forcewake while waiting for an interrupt to arrive, but
> > none for the ACTHD readback.
> > 
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=45181
> > Tested-by: Nicolas Kalkhof nkalkhof()at()web.de
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> Whilst this patch doesn't directly enable the ACTHD w/a, I have observed
> that with a very light load (drawing a single large transformed texture)
> reading back the ACTHD (along with the GT forcewake dance) becomes the
> predominant consumer of CPU time for the system. (The rate-limiting step
> is still the GPU, it just irked me to see the kernel consume more CPU time
> than X.)
> 
> This workaround appears more successful than the last, and doesn't
> appear to break anything else, so
> 
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>

I've picked up patches 1,2 & 4 of this series, thanks for taking a look at
them. I'll postpone 3 until we do the seqno/request refactoring for real,
atm there's too much stuff in this area outstanding and we need to judge
this one in the context of the real thing.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

      reply	other threads:[~2012-02-13  9:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 13:03 [PATCH 1/4] drm/i915: outstanding_lazy_request is a u32 Daniel Vetter
2012-01-25 13:03 ` [PATCH 2/4] drm/i915: fixup seqno allocation logic for lazy_request Daniel Vetter
2012-01-25 14:17   ` Chris Wilson
2012-01-25 15:32     ` [PATCH] " Daniel Vetter
2012-01-25 15:46       ` Chris Wilson
2012-01-26 13:55         ` Daniel Vetter
2012-01-25 13:03 ` [PATCH 3/4] drm/i915: adjust ring->add_request to no longer pass back the seqno Daniel Vetter
2012-01-25 15:33   ` [PATCH] " Daniel Vetter
2012-01-25 13:04 ` [PATCH 4/4] drm/i915: enable forcewake voodoo also for gen6 Daniel Vetter
2012-01-30 22:33   ` Daniel Vetter
2012-02-08 10:00   ` Chris Wilson
2012-02-13 10:00     ` Daniel Vetter [this message]

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=20120213100005.GB5301@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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.