Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 02/25] drm/i915: Mark pin flags as u64
Date: Fri, 2 Nov 2018 16:48:07 +0000	[thread overview]
Message-ID: <720e06d9-113a-52ab-d1c5-8556c51b9258@intel.com> (raw)
In-Reply-To: <20181102161232.17742-2-chris@chris-wilson.co.uk>

On 02/11/2018 16:12, Chris Wilson wrote:
> Since the flags are being used to operate on a u64 variable, they too
> need to be marked as such so that the inverses are full width (and not
> zero extended on 32b kernels and bdw+).
>
> Reported-by: Sergii Romantsov <sergii.romantsov@globallogic.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: stable@vger.kernel.org


Feels like Sergii should have done a v2.

Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>


> ---
>   drivers/gpu/drm/i915/i915_gem_gtt.h | 28 ++++++++++++++--------------
>   1 file changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.h b/drivers/gpu/drm/i915/i915_gem_gtt.h
> index a030299b79cd..4874da09a3c4 100644
> --- a/drivers/gpu/drm/i915/i915_gem_gtt.h
> +++ b/drivers/gpu/drm/i915/i915_gem_gtt.h
> @@ -660,20 +660,20 @@ int i915_gem_gtt_insert(struct i915_address_space *vm,
>   			u64 start, u64 end, unsigned int flags);
>   
>   /* Flags used by pin/bind&friends. */
> -#define PIN_NONBLOCK		BIT(0)
> -#define PIN_MAPPABLE		BIT(1)
> -#define PIN_ZONE_4G		BIT(2)
> -#define PIN_NONFAULT		BIT(3)
> -#define PIN_NOEVICT		BIT(4)
> -
> -#define PIN_MBZ			BIT(5) /* I915_VMA_PIN_OVERFLOW */
> -#define PIN_GLOBAL		BIT(6) /* I915_VMA_GLOBAL_BIND */
> -#define PIN_USER		BIT(7) /* I915_VMA_LOCAL_BIND */
> -#define PIN_UPDATE		BIT(8)
> -
> -#define PIN_HIGH		BIT(9)
> -#define PIN_OFFSET_BIAS		BIT(10)
> -#define PIN_OFFSET_FIXED	BIT(11)
> +#define PIN_NONBLOCK		BIT_ULL(0)
> +#define PIN_MAPPABLE		BIT_ULL(1)
> +#define PIN_ZONE_4G		BIT_ULL(2)
> +#define PIN_NONFAULT		BIT_ULL(3)
> +#define PIN_NOEVICT		BIT_ULL(4)
> +
> +#define PIN_MBZ			BIT_ULL(5) /* I915_VMA_PIN_OVERFLOW */
> +#define PIN_GLOBAL		BIT_ULL(6) /* I915_VMA_GLOBAL_BIND */
> +#define PIN_USER		BIT_ULL(7) /* I915_VMA_LOCAL_BIND */
> +#define PIN_UPDATE		BIT_ULL(8)
> +
> +#define PIN_HIGH		BIT_ULL(9)
> +#define PIN_OFFSET_BIAS		BIT_ULL(10)
> +#define PIN_OFFSET_FIXED	BIT_ULL(11)
>   #define PIN_OFFSET_MASK		(-I915_GTT_PAGE_SIZE)
>   
>   #endif

  reply	other threads:[~2018-11-02 16:48 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 16:12 [PATCH 01/25] RFT drm/i915/execlists: Flush memory before signaling ELSQ Chris Wilson
2018-11-02 16:12 ` [PATCH 02/25] drm/i915: Mark pin flags as u64 Chris Wilson
2018-11-02 16:48   ` Lionel Landwerlin [this message]
2018-11-02 17:22   ` [Intel-gfx] " Michal Wajdeczko
2018-11-02 16:12 ` [PATCH 03/25] drm/i915/selftests: Verify we can perform resets from atomic context Chris Wilson
2018-11-02 16:12 ` [PATCH 04/25] drm/i915/userptr: Avoid struct_mutex recursion for mmu_invalidate_range_start Chris Wilson
2018-11-05 16:45   ` Tvrtko Ursulin
2018-11-06 13:32     ` Daniel Vetter
2018-11-06 12:41   ` Tvrtko Ursulin
2018-11-06 13:02     ` Chris Wilson
2018-11-06 13:11       ` Chris Wilson
2018-11-06 14:11       ` Tvrtko Ursulin
2018-11-02 16:12 ` [PATCH 05/25] drm/i915: Prevent machine hang from Broxton's vtd w/a and error capture Chris Wilson
2018-11-16 11:45   ` Joonas Lahtinen
2018-11-02 16:12 ` [PATCH 06/25] drm/i915: Always try to reset the GPU on takeover Chris Wilson
2018-11-26 10:24   ` Joonas Lahtinen
2018-11-02 16:12 ` [PATCH 07/25] drm/i915: Cache the error string Chris Wilson
2018-11-23 12:52   ` Joonas Lahtinen
2018-11-23 13:01     ` Chris Wilson
2018-11-02 16:12 ` [PATCH 08/25] drm/i915: Report the number of closed vma held by each context in debugfs Chris Wilson
2018-11-26 14:10   ` Tvrtko Ursulin
2018-11-02 16:12 ` [PATCH 09/25] drm/i915: Remove debugfs/i915_ppgtt_info Chris Wilson
2018-11-26 11:09   ` Tvrtko Ursulin
2018-11-02 16:12 ` [PATCH 10/25] drm/i915: Track all held rpm wakerefs Chris Wilson
2018-11-02 16:12 ` [PATCH 11/25] drm/i915: Markup paired operations on wakerefs Chris Wilson
2018-11-02 16:12 ` [PATCH 12/25] drm/i915: Syntatic sugar for using intel_runtime_pm Chris Wilson
2018-11-02 16:12 ` [PATCH 13/25] drm/i915: Markup paired operations on display power domains Chris Wilson
2018-11-02 16:12 ` [PATCH 14/25] drm/i915: Track the wakeref used to initialise " Chris Wilson
2018-11-02 16:12 ` [PATCH 15/25] drm/i915: Combined gt.awake/gt.power wakerefs Chris Wilson
2018-11-02 16:12 ` [PATCH 16/25] drm/i915/dp: Markup pps lock power well Chris Wilson
2018-11-02 16:12 ` [PATCH 17/25] drm/i915: Complain if hsw_get_pipe_config acquires the same power well twice Chris Wilson
2018-11-02 16:12 ` [PATCH 18/25] drm/i915: Mark up Ironlake ips with rpm wakerefs Chris Wilson
2018-11-02 16:12 ` [PATCH 19/25] drm/i915: Serialise concurrent calls to i915_gem_set_wedged() Chris Wilson
2018-11-02 16:12 ` [PATCH 20/25] drm/i915: Differentiate between ggtt->mutex and ppgtt->mutex Chris Wilson
2018-11-26 11:13   ` Tvrtko Ursulin
2018-11-02 16:12 ` [PATCH 21/25] drm/i915: Pull all the reset functionality together into i915_reset.c Chris Wilson
2018-11-02 16:12 ` [PATCH 22/25] drm/i915: Make all GPU resets atomic Chris Wilson
2018-11-02 16:12 ` [PATCH 23/25] drm/i915/guc: Disable global reset Chris Wilson
2018-11-02 16:12 ` [PATCH 24/25] drm/i915: Perform device reset under stop-machine Chris Wilson
2018-11-02 17:46   ` Chris Wilson
2018-11-02 16:12 ` [PATCH 25/25] drm/i915: Remove GPU reset dependence on struct_mutex Chris Wilson
2018-11-02 18:24 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/25] RFT drm/i915/execlists: Flush memory before signaling ELSQ Patchwork
2018-11-02 18:33 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-02 18:48 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-02 21:21 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-11-05 11:40 ` [PATCH 01/25] " Mika Kuoppala

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=720e06d9-113a-52ab-d1c5-8556c51b9258@intel.com \
    --to=lionel.g.landwerlin@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