From: "Michał Winiarski" <michal.winiarski@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: <intel-gfx@lists.freedesktop.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v3] drm/i915: Use two 32bit reads for select 64bit REG_READ ioctls
Date: Fri, 17 Jul 2015 17:10:25 +0200 [thread overview]
Message-ID: <20150717151025.GA26539@mwiniars-desk1.igk.intel.com> (raw)
In-Reply-To: <1437046676-31811-1-git-send-email-chris@chris-wilson.co.uk>
On Thu, Jul 16, 2015 at 12:37:56PM +0100, Chris Wilson wrote:
> Since the hardware sometimes mysteriously totally flummoxes the 64bit
> read of a 64bit register when read using a single instruction, split the
> read into two instructions. Since the read here is of automatically
> incrementing timestamp counters, we also have to be very careful in
> order to make sure that it does not increment between the two
> instructions.
>
> However, since userspace tried to workaround this issue and so enshrined
> this ABI for a broken hardware read and in the process neglected that
> the read only fails in some environments, we have to introduce a new
> uABI flag for userspace to request the 2x32 bit accurate read of the
> timestamp.
>
> v2: Fix alignment check and include details of the workaround for
> userspace.
>
> Reported-by: Karol Herbst <freedesktop@karolherbst.de>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91317
> Testcase: igt/gem_reg_read
Tested-by: Michał Winiarski <michal.winiarski@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michał Winiarski <michal.winiarski@intel.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/gpu/drm/i915/intel_uncore.c | 26 +++++++++++++++++++-------
> include/uapi/drm/i915_drm.h | 8 ++++++++
> 2 files changed, 27 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
> index 2c477663d378..eb244b57b3fd 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -1310,10 +1310,12 @@ int i915_reg_read_ioctl(struct drm_device *dev,
> struct drm_i915_private *dev_priv = dev->dev_private;
> struct drm_i915_reg_read *reg = data;
> struct register_whitelist const *entry = whitelist;
> + unsigned size;
> + u64 offset;
> int i, ret = 0;
>
> for (i = 0; i < ARRAY_SIZE(whitelist); i++, entry++) {
> - if (entry->offset == reg->offset &&
> + if (entry->offset == (reg->offset & -entry->size) &&
> (1 << INTEL_INFO(dev)->gen & entry->gen_bitmask))
> break;
> }
> @@ -1321,23 +1323,33 @@ int i915_reg_read_ioctl(struct drm_device *dev,
> if (i == ARRAY_SIZE(whitelist))
> return -EINVAL;
>
> + /* We use the low bits to encode extra flags as the register should
> + * be naturally aligned (and those that are not so aligned merely
> + * limit the available flags for that register).
> + */
> + offset = entry->offset;
> + size = entry->size;
> + size |= reg->offset ^ offset;
> +
> intel_runtime_pm_get(dev_priv);
>
> - switch (entry->size) {
> + switch (size) {
> + case 8 | 1:
> + reg->val = I915_READ64_2x32(offset, offset+4);
> + break;
> case 8:
> - reg->val = I915_READ64(reg->offset);
> + reg->val = I915_READ64(offset);
> break;
> case 4:
> - reg->val = I915_READ(reg->offset);
> + reg->val = I915_READ(offset);
> break;
> case 2:
> - reg->val = I915_READ16(reg->offset);
> + reg->val = I915_READ16(offset);
> break;
> case 1:
> - reg->val = I915_READ8(reg->offset);
> + reg->val = I915_READ8(offset);
> break;
> default:
> - MISSING_CASE(entry->size);
> ret = -EINVAL;
> goto out;
> }
> diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h
> index b0f82ddab987..83f60f01dca2 100644
> --- a/include/uapi/drm/i915_drm.h
> +++ b/include/uapi/drm/i915_drm.h
> @@ -1087,6 +1087,14 @@ struct drm_i915_reg_read {
> __u64 offset;
> __u64 val; /* Return value */
> };
> +/* Known registers:
> + *
> + * Render engine timestamp - 0x2358 + 64bit - gen7+
> + * - Note this register returns an invalid value if using the default
> + * single instruction 8byte read, in order to workaround that use
> + * offset (0x2538 | 1) instead.
> + *
> + */
>
> struct drm_i915_reset_stats {
> __u32 ctx_id;
> --
> 2.1.4
>
next prev parent reply other threads:[~2015-07-17 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1437045549-15455-1-git-send-email-michal.winiarski@intel.com>
2015-07-16 11:37 ` [PATCH v3] drm/i915: Use two 32bit reads for select 64bit REG_READ ioctls Chris Wilson
2015-07-17 15:10 ` Michał Winiarski [this message]
2015-07-21 6:49 ` [Intel-gfx] " Daniel Vetter
2015-07-21 9:45 ` Chris Wilson
2015-07-21 9:49 ` Daniel Vetter
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=20150717151025.GA26539@mwiniars-desk1.igk.intel.com \
--to=michal.winiarski@intel.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox