public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC][PATCH 2/2] drm/i915: Jump to at least RPe on VLV when increasing the GPU frequency
Date: Wed, 26 Jun 2013 12:24:34 +0200	[thread overview]
Message-ID: <20130626102434.GE18285@phenom.ffwll.local> (raw)
In-Reply-To: <20130625115439.12e0aa3c@jbarnes-desktop>

On Tue, Jun 25, 2013 at 11:54:39AM -0700, Jesse Barnes wrote:
> On Tue, 25 Jun 2013 21:38:11 +0300
> ville.syrjala@linux.intel.com wrote:
> 
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > If the current GPU frquency is below RPe, and we're asked to increase
> > it, just go directly to RPe. This should provide better performance
> > faster than letting the frequency trickle up in response to the up
> > threshold interrupts.
> > 
> > For now just do it for VLV, since that matches quite closely how VLV
> > used to operate when the rps delayed timer kept things at RPe always.
> > 
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> >  drivers/gpu/drm/i915/i915_irq.c | 12 ++++++++++--
> >  1 file changed, 10 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> > index 62f8b2d..d6bd0d7 100644
> > --- a/drivers/gpu/drm/i915/i915_irq.c
> > +++ b/drivers/gpu/drm/i915/i915_irq.c
> > @@ -699,9 +699,17 @@ static void gen6_pm_rps_work(struct work_struct *work)
> >  
> >  	mutex_lock(&dev_priv->rps.hw_lock);
> >  
> > -	if (pm_iir & GEN6_PM_RP_UP_THRESHOLD)
> > +	if (pm_iir & GEN6_PM_RP_UP_THRESHOLD) {
> >  		new_delay = dev_priv->rps.cur_delay + 1;
> > -	else
> > +
> > +		/*
> > +		 * For better performance, jump directly
> > +		 * to RPe if we're below it.
> > +		 */
> > +		if (IS_VALLEYVIEW(dev_priv->dev) &&
> > +		    dev_priv->rps.cur_delay < dev_priv->rps.rpe_delay)
> > +			new_delay = dev_priv->rps.rpe_delay;
> > +	} else
> >  		new_delay = dev_priv->rps.cur_delay - 1;
> >  
> >  	/* sysfs frequency interfaces may have snuck in while servicing the
> 
> Yeah, seems reasonable.  Going to RP1 on other platforms might be a
> good approximation of this.
> 
> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>

Queued for -next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-06-26 10:24 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
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 [this message]
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=20130626102434.GE18285@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