From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [CI 6/6] drm/i915: Remove I915_READ64 and I915_READ64_32x2
Date: Wed, 12 Jun 2019 07:29:33 +0100 [thread overview]
Message-ID: <016c5053-1915-ef59-0630-a7012579d82d@linux.intel.com> (raw)
In-Reply-To: <20190611171125.GH5942@intel.com>
On 11/06/2019 18:11, Ville Syrjälä wrote:
> On Mon, Jun 10, 2019 at 01:06:08PM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Now that all their users are gone we can remove the macros and
>> accompanying duplicated comment.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Suggested-by: Jani Nikula <jani.nikula@intel.com>
>> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_drv.h | 18 ------------------
>> 1 file changed, 18 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>> index 20eb37b760c4..d3c02e009a98 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -2851,24 +2851,6 @@ extern void intel_display_print_error_state(struct drm_i915_error_state_buf *e,
>> #define I915_READ_NOTRACE(reg__) __I915_REG_OP(read_notrace, dev_priv, (reg__))
>> #define I915_WRITE_NOTRACE(reg__, val__) __I915_REG_OP(write_notrace, dev_priv, (reg__), (val__))
>>
>> -/* Be very careful with read/write 64-bit values. On 32-bit machines, they
>> - * will be implemented using 2 32-bit writes in an arbitrary order with
>> - * an arbitrary delay between them. This can cause the hardware to
>> - * act upon the intermediate value, possibly leading to corruption and
>> - * machine death. For this reason we do not support I915_WRITE64, or
>> - * dev_priv->uncore.funcs.mmio_writeq.
>> - *
>> - * When reading a 64-bit value as two 32-bit values, the delay may cause
>> - * the two reads to mismatch, e.g. a timestamp overflowing. Also note that
>> - * occasionally a 64-bit register does not actualy support a full readq
>> - * and must be read using two 32-bit reads.
>> - *
>> - * You have been warned.
>
> We are no longer warned?
Clue is in the word duplicated in the commit message. ;) The exact same
comment exists over in intel_uncore.h above 64-bit accessors and
intel_uncore_read_2x32.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-12 6:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 12:06 [CI 1/6] drm/i915: Eliminate unused mmio accessors Tvrtko Ursulin
2019-06-10 12:06 ` [CI 2/6] drm/i915: Convert i915_reg_read_ioctl to use explicit " Tvrtko Ursulin
2019-06-10 12:06 ` [CI 3/6] drm/i915: Convert icl_get_stolen_reserved to uncore " Tvrtko Ursulin
2019-06-10 12:06 ` [CI 4/6] drm/i915: Convert gem_record_fences " Tvrtko Ursulin
2019-06-10 12:06 ` [CI 5/6] drm/i915: Convert intel_read_wm_latency " Tvrtko Ursulin
2019-06-10 12:06 ` [CI 6/6] drm/i915: Remove I915_READ64 and I915_READ64_32x2 Tvrtko Ursulin
2019-06-11 17:11 ` Ville Syrjälä
2019-06-12 6:29 ` Tvrtko Ursulin [this message]
2019-06-10 15:11 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/6] drm/i915: Eliminate unused mmio accessors Patchwork
2019-06-11 12:27 ` ✓ 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=016c5053-1915-ef59-0630-a7012579d82d@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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