From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC][PATCH 1/2] drm/i915: Don't increase the GPU frequency from the delayed VLV rps timer
Date: Wed, 26 Jun 2013 12:21:31 +0200 [thread overview]
Message-ID: <20130626102131.GD18285@phenom.ffwll.local> (raw)
In-Reply-To: <20130625115328.593abf46@jbarnes-desktop>
On Tue, Jun 25, 2013 at 11:53:28AM -0700, Jesse Barnes wrote:
> On Tue, 25 Jun 2013 21:38:10 +0300
> ville.syrjala@linux.intel.com wrote:
>
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > There's little point in increasing the GPU frequency from the delayed
> > rps work on VLV. Now when the GPU is idle, the GPU frequency actually
> > keeps dropping gradually until it hits the minimum, whereas previously
> > it just ping-ponged constantly between RPe and RPe-1.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_pm.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index 96cfb3e..eaf0fa2 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -3464,7 +3464,8 @@ static void vlv_rps_timer_work(struct work_struct *work)
> > * min freq available.
> > */
> > mutex_lock(&dev_priv->rps.hw_lock);
> > - valleyview_set_rps(dev_priv->dev, dev_priv->rps.rpe_delay);
> > + if (dev_priv->rps.cur_delay > dev_priv->rps.rpe_delay)
> > + valleyview_set_rps(dev_priv->dev, dev_priv->rps.rpe_delay);
> > mutex_unlock(&dev_priv->rps.hw_lock);
> > }
> >
>
> Hm that's not what I saw here; I stopped getting the timer interrupts
> when the GPU went idle. But that could be explained by punit fw
> differences.
>
> So this change looks ok to me.
>
> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Queued for -next, thanks for the patch. In case you noodle around in here
some more, I'd also vote for a s/timer_work/delayed_work/ color change:
The execution enviroment of a time is _much_ different than from a work,
so sticking to consistent naming helps in reading code.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-06-26 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 18:38 [RFC][PATCH 0/2] drm/i915: VLV rps timer changes ville.syrjala
2013-06-25 18:38 ` [RFC][PATCH 1/2] drm/i915: Don't increase the GPU frequency from the delayed VLV rps timer ville.syrjala
2013-06-25 18:53 ` Jesse Barnes
2013-06-26 10:21 ` Daniel Vetter [this message]
2013-06-25 18:38 ` [RFC][PATCH 2/2] drm/i915: Jump to at least RPe on VLV when increasing the GPU frequency ville.syrjala
2013-06-25 18:54 ` Jesse Barnes
2013-06-26 10:24 ` Daniel Vetter
2013-06-25 18:43 ` [RFC][PATCH 0/2] drm/i915: VLV rps timer changes 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=20130626102131.GD18285@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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