From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>,
Paulo Zanoni <paulo.r.zanoni@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] drm/i915: Fix runtime pm inbalance due to reg I/O forcewake dance
Date: Fri, 14 Mar 2014 10:34:36 +0200 [thread overview]
Message-ID: <20140314083436.GU20292@intel.com> (raw)
In-Reply-To: <20140314082400.GB17305@nuc-i3427.alporthouse.com>
On Fri, Mar 14, 2014 at 08:24:00AM +0000, Chris Wilson wrote:
> On Fri, Mar 14, 2014 at 10:18:47AM +0200, Ville Syrjälä wrote:
> > On Fri, Mar 14, 2014 at 08:48:46AM +0100, Daniel Vetter wrote:
> > > This regression has been introduced in
> > >
> > > commit 8232644ccf099548710843e97360a3fcd6d28e04
> > > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > > Date: Wed Mar 5 12:00:39 2014 +0000
> > >
> > > drm/i915: Convert the forcewake worker into a timer func
> > >
> > > which started to use the delayed forcewake put also for the register
> > > I/O forcewake dance. But this conflicts functionally with the
> > > (reviewed in parallel)
> > >
> > > commit 6d88064edcfc5e5893371f7c06b9f3078dc1edf6
> > > Author: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > > Date: Fri Feb 21 17:58:29 2014 -0300
> > >
> > > drm/i915: put runtime PM only when we actually release force_wake
> > >
> > > which moved the runtime pm put calls into the delayed forcewake put
> > > function to avoid an inversion between these. The problem is that the
> > > register I/O function do _not_ grab a runtime pm reference, hence
> > > dropping it is a bug.
> > >
> > > So split the timer into two to re-balance the runtime pm refcounting.
> > > The tricky bit to ensure is that the _raw timer doesn't run after
> > > we've runtime-suspended the device. After all it only has an implicit
> > > runtime pm reference provided by its caller. But the del_timer_sync in
> > > the runtime suspend code will ensure this.
> > >
> > > Add a comment to document this all.
> >
> > Yuck. Why don't we just stick the runtime pm put into
> > gen6_gt_force_wake_put() and let Chris's timer cancellation +
> > forcewake reset fixes take care of things?
>
> Heh, I went the other way round, dropped the runtime pm put from the
> timer and flushed the forcewaker timer when we suspended the device...
That's what I meant. No delayed runtime_pm_put.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-03-14 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 7:48 [PATCH] drm/i915: Fix runtime pm inbalance due to reg I/O forcewake dance Daniel Vetter
2014-03-14 8:18 ` Ville Syrjälä
2014-03-14 8:24 ` Chris Wilson
2014-03-14 8:34 ` Ville Syrjälä [this message]
2014-03-14 8:52 ` Daniel Vetter
2014-03-14 18:25 ` Jesse Barnes
2014-03-14 8:37 ` [PATCH] drm/i915: Rebalance runtime pm vs forcewake Chris Wilson
2014-03-14 15:51 ` Daniel Vetter
2014-03-14 16:13 ` Chris Wilson
2014-03-14 18:43 ` Daniel Vetter
2014-03-31 18:22 ` Paulo Zanoni
2014-03-31 18:59 ` Daniel Vetter
2014-04-01 8:14 ` Chris Wilson
2014-04-01 12:32 ` Paulo Zanoni
2014-04-01 12:42 ` Chris Wilson
2014-04-01 17:00 ` 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=20140314083436.GU20292@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=paulo.r.zanoni@intel.com \
/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.