All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Acquire RPM wakeref for KMS atomic commit
Date: Mon, 21 Dec 2015 16:14:53 +0000	[thread overview]
Message-ID: <20151221161453.GL28538@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20151221160208.GG30437@phenom.ffwll.local>

On Mon, Dec 21, 2015 at 05:02:08PM +0100, Daniel Vetter wrote:
> On Sat, Dec 19, 2015 at 09:58:43AM +0000, Chris Wilson wrote:
> > Once all the preparations are complete, we are ready to write the
> > modesetting to the hardware. During this phase, we will be making lots
> > of HW register access, so take a top level wakeref to prevent an
> > unwarranted rpm suspend cycle mid-commit. Lower level functions should
> > be waking the individual power wells as required.
> > 
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93439
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Imre Deak <imre.deak@intel.com>
> 
> The original idea here was that doing this will paper over bugs in our rpm
> refcounting. There's also the problem that for modeset stuff we have all
> the power wells still to take care of.
> 
> For the referenced bug we should add a power domain check in the get hw
> state function instead, which is what we've been doing with all the other
> similar hw state readout functions too.

Agreed that there is another bug, but in the long term, we do want a
"prolonged" wakeref here. In the next evolution of the wakeref assertions,
we should be able to differentiate between the two (i.e. when we have
fine grained wakerefs around the hw access, we need to assert we hold one
of that type in the mmio accessor, rather than the prolonged version).
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-12-21 16:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19  9:58 [PATCH] drm/i915: Acquire RPM wakeref for KMS atomic commit Chris Wilson
2015-12-19 10:49 ` ✗ warning: Fi.CI.BAT Patchwork
2015-12-21 10:37 ` Patchwork
2015-12-21 16:02 ` [PATCH] drm/i915: Acquire RPM wakeref for KMS atomic commit Daniel Vetter
2015-12-21 16:14   ` Chris Wilson [this message]
2015-12-21 16:28     ` Daniel Vetter
2015-12-21 16:37       ` Chris Wilson
2015-12-21 18:21         ` Daniel Vetter
2015-12-22 20:46           ` Chris Wilson
2016-01-14 16:50 ` Imre Deak
2016-01-21 11:52   ` Joonas Lahtinen
2016-01-22  9:21     ` Imre Deak

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=20151221161453.GL28538@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel@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.