From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/i915: Limit the number of loops for reading a split 64bit register
Date: Wed, 09 Sep 2015 11:13:10 +0300 [thread overview]
Message-ID: <87wpw0m2nd.fsf@intel.com> (raw)
In-Reply-To: <20150908190059.GG2767@phenom.ffwll.local>
On Tue, 08 Sep 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Sep 08, 2015 at 02:17:13PM +0100, Chris Wilson wrote:
>> In I915_READ64_2x32 we attempt to read a 64bit register using 2 32bit
>> reads. Due to the nature of the registers we try to read in this manner,
>> they may increment between the two instruction (e.g. a timestamp
>> counter). To keep the result accurate, we repeat the read if we detect
>> an overflow (i.e. the upper value varies). However, some harware is just
>> plain flaky and may endless loop as the the upper 32bits are not stable.
>> Just give up after a couple of tries and report whatever we read last.
>>
>> v2: Use the most recent values when erring out on an unstable register.
>>
>> Reported-by: russianneuromancer@ya.ru
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91906
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Michał Winiarski <michal.winiarski@intel.com>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: stable@vger.kernel.org
>
> Still Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Pushed to drm-intel-next-fixes, thanks for the patch and review.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/i915_drv.h | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>> index 12870073d58f..51a88e70a6f7 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -3402,13 +3402,13 @@ int intel_freq_opcode(struct drm_i915_private *dev_priv, int val);
>> #define I915_READ64(reg) dev_priv->uncore.funcs.mmio_readq(dev_priv, (reg), true)
>>
>> #define I915_READ64_2x32(lower_reg, upper_reg) ({ \
>> - u32 upper, lower, tmp; \
>> - tmp = I915_READ(upper_reg); \
>> + u32 upper, lower, old_upper, loop = 0; \
>> + upper = I915_READ(upper_reg); \
>> do { \
>> - upper = tmp; \
>> + old_upper = upper; \
>> lower = I915_READ(lower_reg); \
>> - tmp = I915_READ(upper_reg); \
>> - } while (upper != tmp); \
>> + upper = I915_READ(upper_reg); \
>> + } while (upper != old_upper && loop++ < 2); \
>> (u64)upper << 32 | lower; })
>>
>> #define POSTING_READ(reg) (void)I915_READ_NOTRACE(reg)
>> --
>> 2.5.1
>>
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
"Michał Winiarski" <michal.winiarski@intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/i915: Limit the number of loops for reading a split 64bit register
Date: Wed, 09 Sep 2015 11:13:10 +0300 [thread overview]
Message-ID: <87wpw0m2nd.fsf@intel.com> (raw)
In-Reply-To: <20150908190059.GG2767@phenom.ffwll.local>
On Tue, 08 Sep 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Sep 08, 2015 at 02:17:13PM +0100, Chris Wilson wrote:
>> In I915_READ64_2x32 we attempt to read a 64bit register using 2 32bit
>> reads. Due to the nature of the registers we try to read in this manner,
>> they may increment between the two instruction (e.g. a timestamp
>> counter). To keep the result accurate, we repeat the read if we detect
>> an overflow (i.e. the upper value varies). However, some harware is just
>> plain flaky and may endless loop as the the upper 32bits are not stable.
>> Just give up after a couple of tries and report whatever we read last.
>>
>> v2: Use the most recent values when erring out on an unstable register.
>>
>> Reported-by: russianneuromancer@ya.ru
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91906
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Michał Winiarski <michal.winiarski@intel.com>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: stable@vger.kernel.org
>
> Still Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Pushed to drm-intel-next-fixes, thanks for the patch and review.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/i915_drv.h | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>> index 12870073d58f..51a88e70a6f7 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -3402,13 +3402,13 @@ int intel_freq_opcode(struct drm_i915_private *dev_priv, int val);
>> #define I915_READ64(reg) dev_priv->uncore.funcs.mmio_readq(dev_priv, (reg), true)
>>
>> #define I915_READ64_2x32(lower_reg, upper_reg) ({ \
>> - u32 upper, lower, tmp; \
>> - tmp = I915_READ(upper_reg); \
>> + u32 upper, lower, old_upper, loop = 0; \
>> + upper = I915_READ(upper_reg); \
>> do { \
>> - upper = tmp; \
>> + old_upper = upper; \
>> lower = I915_READ(lower_reg); \
>> - tmp = I915_READ(upper_reg); \
>> - } while (upper != tmp); \
>> + upper = I915_READ(upper_reg); \
>> + } while (upper != old_upper && loop++ < 2); \
>> (u64)upper << 32 | lower; })
>>
>> #define POSTING_READ(reg) (void)I915_READ_NOTRACE(reg)
>> --
>> 2.5.1
>>
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-09-09 8:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 7:24 [PATCH] drm/i915: Limit the number of loops for reading a split 64bit register Chris Wilson
2015-09-08 7:51 ` Chris Wilson
2015-09-08 9:29 ` Daniel Vetter
2015-09-08 9:29 ` Daniel Vetter
2015-09-08 12:36 ` Jani Nikula
2015-09-08 12:36 ` [Intel-gfx] " Jani Nikula
2015-09-08 13:10 ` Chris Wilson
2015-09-08 13:17 ` [PATCH v2] " Chris Wilson
2015-09-08 19:00 ` Daniel Vetter
2015-09-08 19:00 ` Daniel Vetter
2015-09-09 8:13 ` Jani Nikula [this message]
2015-09-09 8:13 ` Jani Nikula
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=87wpw0m2nd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.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.