From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Len Brown <len.brown@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Extend residency counter ranges on chv and byt
Date: Thu, 2 Mar 2017 20:13:31 +0200 [thread overview]
Message-ID: <20170302181331.GI31595@intel.com> (raw)
In-Reply-To: <1488477700-30550-1-git-send-email-mika.kuoppala@intel.com>
On Thu, Mar 02, 2017 at 08:01:40PM +0200, Mika Kuoppala wrote:
> We were passively acting on the high counter value bit
> and as it was never set, we were only utilizing the
> the 32bits of resolution. As the divisor with these platforms
> is quite high, the wrap around happened in the less than 13 seconds.
>
> If we toggle the resolution bit in the control register and
Can't be done on all machines. IIRC both Chris and me tried this at
some point and on some machines the register was locked. Also I'm
not sure if some piece of firmware depends on the original setting.
> read twice we can get 8 bits more, bringing the wrap in
> 54 minute range.
>
> Reported-by: Len Brown <len.brown@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Len Brown <len.brown@intel.com>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
> drivers/gpu/drm/i915/i915_sysfs.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_sysfs.c b/drivers/gpu/drm/i915/i915_sysfs.c
> index af0ac9f..807d7be 100644
> --- a/drivers/gpu/drm/i915/i915_sysfs.c
> +++ b/drivers/gpu/drm/i915/i915_sysfs.c
> @@ -53,17 +53,26 @@ static u32 calc_residency(struct drm_i915_private *dev_priv,
>
> /* On VLV and CHV, residency time is in CZ units rather than 1.28us */
> if (IS_VALLEYVIEW(dev_priv) || IS_CHERRYVIEW(dev_priv)) {
> - units = 1;
> + u32 lower, upper;
> div = dev_priv->czclk_freq;
>
> - if (I915_READ(VLV_COUNTER_CONTROL) & VLV_COUNT_RANGE_HIGH)
> - units <<= 8;
> + I915_WRITE(VLV_COUNTER_CONTROL,
> + _MASKED_BIT_ENABLE(VLV_COUNT_RANGE_HIGH));
> + upper = I915_READ(reg);
> +
> + I915_WRITE(VLV_COUNTER_CONTROL,
> + _MASKED_BIT_DISABLE(VLV_COUNT_RANGE_HIGH));
> + lower = I915_READ(reg);
> +
> + raw_time = lower | (u64)upper << 8;
> + goto out;
> } else if (IS_GEN9_LP(dev_priv)) {
> units = 1;
> div = 1200; /* 833.33ns */
> }
>
> raw_time = I915_READ(reg) * units;
> + out:
> ret = DIV_ROUND_UP_ULL(raw_time, div);
>
> intel_runtime_pm_put(dev_priv);
> --
> 2.7.4
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-02 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 18:01 [PATCH] drm/i915: Extend residency counter ranges on chv and byt Mika Kuoppala
2017-03-02 18:13 ` Chris Wilson
2017-03-02 18:19 ` Chris Wilson
2017-03-02 18:20 ` Mika Kuoppala
2017-03-02 18:34 ` Chris Wilson
2017-03-02 18:13 ` Ville Syrjälä [this message]
2017-03-02 18:18 ` Mika Kuoppala
2017-03-02 18:21 ` Chris Wilson
2017-03-02 19:15 ` Ville Syrjälä
2017-03-03 8:11 ` Mika Kuoppala
2017-03-02 19:47 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-03-03 14:16 ` [PATCH] " Chris Wilson
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=20170302181331.GI31595@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=len.brown@intel.com \
--cc=mika.kuoppala@linux.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 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.