Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/rps: Add frequency translation helpers
Date: Wed, 4 Dec 2019 13:06:19 +0200	[thread overview]
Message-ID: <20191204110619.GA2018@intel.intel> (raw)
In-Reply-To: <157545662134.9581.16726619588312132709@skylake-alporthouse-com>

Hi Chris,

> > @@ -1633,21 +1633,11 @@ static int i915_rps_boost_info(struct seq_file *m, void *data)
> >  {
> >         struct drm_i915_private *dev_priv = node_to_i915(m->private);
> >         struct intel_rps *rps = &dev_priv->gt.rps;
> > -       u32 act_freq = rps->cur_freq;
> > +       u32 act_freq;
> >         intel_wakeref_t wakeref;
> >  
> > -       with_intel_runtime_pm_if_in_use(&dev_priv->runtime_pm, wakeref) {
> > -               if (IS_VALLEYVIEW(dev_priv) || IS_CHERRYVIEW(dev_priv)) {
> > -                       vlv_punit_get(dev_priv);
> > -                       act_freq = vlv_punit_read(dev_priv,
> > -                                                 PUNIT_REG_GPU_FREQ_STS);
> > -                       vlv_punit_put(dev_priv);
> > -                       act_freq = (act_freq >> 8) & 0xff;
> > -               } else {
> > -                       act_freq = intel_get_cagf(rps,
> > -                                                 I915_READ(GEN6_RPSTAT1));
> > -               }
> > -       }
> > +       with_intel_runtime_pm_if_in_use(&dev_priv->runtime_pm, wakeref)
> > +               act_freq = intel_cagf_freq_read(rps);
> >  
> >         seq_printf(m, "RPS enabled? %d\n", rps->enabled);
> >         seq_printf(m, "GPU busy? %s\n", yesno(dev_priv->gt.awake));
> > @@ -1655,8 +1645,7 @@ static int i915_rps_boost_info(struct seq_file *m, void *data)
> >                    atomic_read(&rps->num_waiters));
> >         seq_printf(m, "Interactive? %d\n", READ_ONCE(rps->power.interactive));
> >         seq_printf(m, "Frequency requested %d, actual %d\n",
> > -                  intel_gpu_freq(rps, rps->cur_freq),
> > -                  intel_gpu_freq(rps, act_freq));
> > +                  intel_gpu_freq(rps, rps->cur_freq), act_freq);
> >         seq_printf(m, "  min hard:%d, soft:%d; max soft:%d, hard:%d\n",
> >                    intel_gpu_freq(rps, rps->min_freq),
> >                    intel_gpu_freq(rps, rps->min_freq_softlimit),
> 
> Good start, but this needs to be rps-centric, please could you pull it
> under intel_rps.c as intel_rps_show (or _dump, or _print), taking a
> struct drm_printer to direct the output.

yes, of course! There are still few rps leftovers around :)

Thanks,
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-12-04 11:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 10:30 [Intel-gfx] [PATCH] drm/i915/rps: Add frequency translation helpers Andi Shyti
2019-12-04 10:50 ` Chris Wilson
2019-12-04 11:06   ` Andi Shyti [this message]
2019-12-04 11:33 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " 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=20191204110619.GA2018@intel.intel \
    --to=andi.shyti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox