From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v5] drm/i915: Handle RC6 counter wrap
Date: Tue, 13 Feb 2018 17:42:24 +0200 [thread overview]
Message-ID: <20180213154224.GH5453@intel.com> (raw)
In-Reply-To: <5e034030-a6ce-4400-b387-39a01301d9f4@linux.intel.com>
On Tue, Feb 13, 2018 at 02:09:51PM +0000, Tvrtko Ursulin wrote:
>
> On 08/02/2018 16:04, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2018-02-08 16:00:36)
> >> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >>
> >> We can implement limited RC6 counter wrap-around protection under the
> >> assumption that clients will be reading this value more frequently than
> >> the wrap period on a given platform.
> >>
> >> With the typical wrap-around period being ~90 minutes, even with the
> >> exception of Baytrail which wraps every 13 seconds, this sounds like a
> >> reasonable assumption.
> >>
> >> Implementation works by storing a 64-bit software copy of a hardware RC6
> >> counter, along with the previous HW counter snapshot. This enables it to
> >> detect wrap is polled frequently enough and keep the software copy
> >> monotonically incrementing.
> >>
> >> v2:
> >> * Missed GEN6_GT_GFX_RC6_LOCKED when considering slot sizing and
> >> indexing.
> >> * Fixed off-by-one in wrap-around handling. (Chris Wilson)
> >>
> >> v3:
> >> * Simplify index checking by using unsigned int. (Chris Wilson)
> >> * Expand the comment to explain why indexing works.
> >>
> >> v4:
> >> * Use __int128 if supported.
> >>
> >> v5:
> >> * Use mul_u64_u32_div. (Chris Wilson)
> >>
> >> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> >> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94852
> >> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> >> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> # v3
> >> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > Ville better not complain he liked the round up behaviour :-p
>
> Ping Ville - ack?
ack
--
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:[~2018-02-13 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <151807682017.28809.17040553218386245341@mail.alporthouse.com151807682017.28809.17040553218386245341@mail.alporthouse.com>
2018-02-08 8:18 ` [PATCH v3] drm/i915: Handle RC6 counter wrap Tvrtko Ursulin
2018-02-08 14:06 ` Ville Syrjälä
2018-02-08 14:31 ` Tvrtko Ursulin
2018-02-08 14:44 ` Chris Wilson
2018-02-08 15:46 ` [PATCH v4] " Tvrtko Ursulin
2018-02-08 15:49 ` Tvrtko Ursulin
2018-02-08 15:51 ` Chris Wilson
2018-02-08 16:00 ` [PATCH v5] " Tvrtko Ursulin
2018-02-08 16:04 ` Chris Wilson
2018-02-13 14:09 ` Tvrtko Ursulin
2018-02-13 15:42 ` Ville Syrjälä [this message]
2018-02-08 9:08 ` ✓ Fi.CI.BAT: success for drm/i915: Handle RC6 counter wrap (rev3) Patchwork
2018-02-08 12:46 ` ✓ Fi.CI.IGT: " Patchwork
2018-02-08 16:04 ` ✓ Fi.CI.BAT: success for drm/i915: Handle RC6 counter wrap (rev4) Patchwork
2018-02-08 16:23 ` ✓ Fi.CI.BAT: success for drm/i915: Handle RC6 counter wrap (rev5) Patchwork
2018-02-13 16:33 ` Tvrtko Ursulin
2018-02-08 23:44 ` ✓ Fi.CI.IGT: " 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=20180213154224.GH5453@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox