All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Show actual along side request frequency in debugfs/i915_rps_boost_info
Date: Tue, 2 Oct 2018 18:46:55 +0300	[thread overview]
Message-ID: <20181002154655.GC9144@intel.com> (raw)
In-Reply-To: <153847871143.23109.16759817945572325601@skylake-alporthouse-com>

On Tue, Oct 02, 2018 at 12:11:51PM +0100, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-10-02 12:02:26)
> > 
> > On 02/10/2018 09:36, Chris Wilson wrote:
> > > Previously we hesitated in adding the hw probe for the actual GPU
> > > frequency for rps_boost as it is quite cumbersome, but given some
> > > surprising HW behaviour it would be useful to know both the RPS boost
> > > state and the actual HW state in one location.
> > > 
> > > Reported-by: Tomi Sarvela <tomi.p.sarvela@intel.com>
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > ---
> > >   drivers/gpu/drm/i915/i915_debugfs.c | 19 +++++++++++++++++--
> > >   1 file changed, 17 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> > > index b4744a68cd88..ce17a53b3a66 100644
> > > --- a/drivers/gpu/drm/i915/i915_debugfs.c
> > > +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> > > @@ -2215,8 +2215,22 @@ static int i915_rps_boost_info(struct seq_file *m, void *data)
> > >       struct drm_i915_private *dev_priv = node_to_i915(m->private);
> > >       struct drm_device *dev = &dev_priv->drm;
> > >       struct intel_rps *rps = &dev_priv->gt_pm.rps;
> > > +     u32 act_freq = rps->cur_freq;
> > >       struct drm_file *file;
> > >   
> > > +     if (intel_runtime_pm_get_if_in_use(dev_priv)) {
> > > +             if (IS_VALLEYVIEW(dev_priv) || IS_CHERRYVIEW(dev_priv)) {
> > > +                     mutex_lock(&dev_priv->pcu_lock);
> > > +                     act_freq = vlv_punit_read(dev_priv,
> > > +                                               PUNIT_REG_GPU_FREQ_STS);
> > 
> > There is another read site for this reg which right shifts and masks 
> > before passing to intel_gpu_freq. Who is right and who is wrong? :)
> 
> Considering that's where I copied from... Oops.

Worth adding intel_gpu_act_freq() or something?

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-10-02 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02  8:36 [PATCH] drm/i915: Show actual along side request frequency in debugfs/i915_rps_boost_info Chris Wilson
2018-10-02 10:54 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-10-02 11:02 ` [PATCH] " Tvrtko Ursulin
2018-10-02 11:11   ` Chris Wilson
2018-10-02 15:46     ` Ville Syrjälä [this message]
2018-10-02 16:01       ` Chris Wilson
2018-10-02 11:32 ` [PATCH v2] drm/i915: Show actual alongside requested " Chris Wilson
2018-10-02 11:41   ` Tvrtko Ursulin
2018-10-02 11:47     ` Chris Wilson
2018-10-02 12:24 ` ✓ Fi.CI.BAT: success for drm/i915: Show actual along side request frequency in debugfs/i915_rps_boost_info (rev2) Patchwork
2018-10-02 20:47 ` ✗ Fi.CI.IGT: failure " Patchwork

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=20181002154655.GC9144@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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.