From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
oscar.mateo@intel.com, intel-gfx@lists.freedesktop.org,
Greg KH <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] [PATCH 45/53] drm/i915/bdw: Do not call intel_runtime_pm_get() in an interrupt
Date: Fri, 8 Aug 2014 11:37:01 +0200 [thread overview]
Message-ID: <20140808093701.GO8727@phenom.ffwll.local> (raw)
In-Reply-To: <20140808092040.GD3021@nuc-i3427.alporthouse.com>
On Fri, Aug 08, 2014 at 10:20:40AM +0100, Chris Wilson wrote:
> On Tue, Jul 29, 2014 at 12:26:36PM +0200, Daniel Vetter wrote:
> > On Tue, Jul 29, 2014 at 08:37:48AM +0100, Chris Wilson wrote:
> > > On Mon, Jul 28, 2014 at 10:54:06AM +0200, Daniel Vetter wrote:
> > > > On Sat, Jul 26, 2014 at 11:27:38AM +0100, Chris Wilson wrote:
> > > > > On Wed, Jun 18, 2014 at 10:54:13PM +0200, Daniel Vetter wrote:
> > > > > > On Fri, Jun 13, 2014 at 04:38:03PM +0100, oscar.mateo@intel.com wrote:
> > > > > > > From: Oscar Mateo <oscar.mateo@intel.com>
> > > > > > >
> > > > > > > Or with a spinlock grabbed, because it might sleep, which is not
> > > > > > > a nice thing to do. Instead, do the runtime_pm get/put together
> > > > > > > with the create/destroy request, and handle the forcewake get/put
> > > > > > > directly.
> > > > > > >
> > > > > > > Signed-off-by: Oscar Mateo <oscar.mateo@intel.com>
> > > > > >
> > > > > > Looks like a fixup that should be squashed into relevant earlier patches.
> > > > >
> > > > > The whole gen6_gt_force_wake_get() calling intel_runtime_pm_get() is
> > > > > broken due to this - we must be able to read registers in atomic
> > > > > context!
> > > > >
> > > > > Please revert c8c8fb33b37766acf6474784b0d5245dab9a1690
> > > >
> > > > force_wake_get can't call runtime_pm_get becuase pm_get can sleep. So if
> > > > you want to read registers from atomic context you have to have a runtime
> > > > pm reference from someone else.
> > >
> > > Nope. That cannot work.
> >
> > Well it works currently. So where do you see the problem?
>
> Sampling registers from an timer - in particular, we really do not want
> to disable runtime pm whilst trying to monitor the impact of runtime pm.
In that case you can grab a runtime pm reference iff the device is powered
on already. Which won't call anything scary, just amounts to an
atomic_add_unless or so, and then drop it again.
Unfortunately there doesn't seem to be such a thing around already, so
need to add it first. Greg, how much would you freak out if we add
something like
/**
* pm_runtime_get_unless_suspended - grab a rpm ref if the device is on
*
* Returns true if an rpm ref has been acquire, false otherwise. Can be
* called from atomic context to e.g. sample perfomance counters (where we
* obviously don't want to disturb system state if everything is off atm).
*/
static inline bool pm_runtime_get_unless_suspended(struct device *dev)
{
return atomic_add_unless(&dev->power.usage_count, 1, 0);
}
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next parent reply other threads:[~2014-08-08 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1402673891-14618-1-git-send-email-oscar.mateo@intel.com>
[not found] ` <1402673891-14618-46-git-send-email-oscar.mateo@intel.com>
[not found] ` <20140618205413.GH5821@phenom.ffwll.local>
[not found] ` <20140726102738.GA21056@nuc-i3427.alporthouse.com>
[not found] ` <20140728085406.GX4747@phenom.ffwll.local>
[not found] ` <20140729073748.GD21570@nuc-i3427.alporthouse.com>
[not found] ` <20140729102636.GK4747@phenom.ffwll.local>
[not found] ` <20140808092040.GD3021@nuc-i3427.alporthouse.com>
2014-08-08 9:37 ` Daniel Vetter [this message]
2014-08-08 13:41 ` [Intel-gfx] [PATCH 45/53] drm/i915/bdw: Do not call intel_runtime_pm_get() in an interrupt Greg KH
2014-08-09 0:18 ` Rafael J. Wysocki
2014-08-09 0:14 ` Rafael J. Wysocki
2014-08-09 1:21 ` Alan Stern
2014-08-09 8:53 ` Daniel Vetter
2014-08-10 1:55 ` Rafael J. Wysocki
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=20140808093701.GO8727@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oscar.mateo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox