From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v3] drm/xe: Reinstate pipelined fence enable_signaling
Date: Wed, 27 Sep 2023 15:17:19 +0300 [thread overview]
Message-ID: <87r0mjkdyo.fsf@intel.com> (raw)
In-Reply-To: <20230915172606.14436-1-thomas.hellstrom@linux.intel.com>
On Fri, 15 Sep 2023, Thomas Hellström <thomas.hellstrom@linux.intel.com> wrote:
> With the GPUVA conversion, the xe_bo::vmas member became replaced with
> drm_gem_object::gpuva.list, however there was a couple of usage instances
> left using the old member. Most notably the pipelined fence
> enable_signaling.
>
> Remove the xe_bo::vmas member completely, fix usage instances and
> also enable this pipelined fence enable_signaling even for faulting
> VM:s since we actually wait for bind fences to complete.
>
> v2:
> - Rebase.
> v3:
> - Fix display code build error.
>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_fb.c | 2 +-
Commits touching i915 should be separated from the rest, regardless of
leaving a broken commit in the middle. Combining i915 and xe changes
leads to conflicts that need to be addressed when rebasing drm-xe-next
for upstream submission. Separate patches are easier to deal with, and
squash to other patches.
No core xe enabling patch can be sent upstream with i915 changes.
BR,
Jani.
> drivers/gpu/drm/xe/xe_bo.c | 5 ++---
> drivers/gpu/drm/xe/xe_bo_types.h | 2 --
> drivers/gpu/drm/xe/xe_pt.c | 2 +-
> 4 files changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_fb.c b/drivers/gpu/drm/i915/display/intel_fb.c
> index f5a96b94cfba..d5b9b0255c6a 100644
> --- a/drivers/gpu/drm/i915/display/intel_fb.c
> +++ b/drivers/gpu/drm/i915/display/intel_fb.c
> @@ -2012,7 +2012,7 @@ int intel_framebuffer_init(struct intel_framebuffer *intel_fb,
> * mode when the object is VM_BINDed, so we can only set
> * coherency with display when unbound.
> */
> - if (XE_IOCTL_DBG(dev_priv, !list_empty(&obj->vmas))) {
> + if (XE_IOCTL_DBG(dev_priv, !list_empty(&obj->ttm.base.gpuva.list))) {
> ttm_bo_unreserve(&obj->ttm);
> goto err;
> }
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index 27726d4f3423..c5e4d04c4d58 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -455,7 +455,7 @@ static int xe_bo_trigger_rebind(struct xe_device *xe, struct xe_bo *bo,
>
> dma_resv_assert_held(bo->ttm.base.resv);
>
> - if (!xe_device_in_fault_mode(xe) && !list_empty(&bo->vmas)) {
> + if (!list_empty(&bo->ttm.base.gpuva.list)) {
> dma_resv_iter_begin(&cursor, bo->ttm.base.resv,
> DMA_RESV_USAGE_BOOKKEEP);
> dma_resv_for_each_fence_unlocked(&cursor, fence)
> @@ -1046,7 +1046,7 @@ static void xe_ttm_bo_destroy(struct ttm_buffer_object *ttm_bo)
> drm_prime_gem_destroy(&bo->ttm.base, NULL);
> drm_gem_object_release(&bo->ttm.base);
>
> - xe_assert(xe, list_empty(&bo->vmas));
> + xe_assert(xe, list_empty(&ttm_bo->base.gpuva.list));
>
> if (bo->ggtt_node.size)
> xe_ggtt_remove_bo(bo->tile->mem.ggtt, bo);
> @@ -1229,7 +1229,6 @@ struct xe_bo *__xe_bo_create_locked(struct xe_device *xe, struct xe_bo *bo,
> bo->props.preferred_gt = XE_BO_PROPS_INVALID;
> bo->props.preferred_mem_type = XE_BO_PROPS_INVALID;
> bo->ttm.priority = DRM_XE_VMA_PRIORITY_NORMAL;
> - INIT_LIST_HEAD(&bo->vmas);
> INIT_LIST_HEAD(&bo->pinned_link);
>
> drm_gem_private_object_init(&xe->drm, &bo->ttm.base, size);
> diff --git a/drivers/gpu/drm/xe/xe_bo_types.h b/drivers/gpu/drm/xe/xe_bo_types.h
> index 2ea9ad423170..946427fd3fe8 100644
> --- a/drivers/gpu/drm/xe/xe_bo_types.h
> +++ b/drivers/gpu/drm/xe/xe_bo_types.h
> @@ -31,8 +31,6 @@ struct xe_bo {
> struct xe_vm *vm;
> /** @tile: Tile this BO is attached to (kernel BO only) */
> struct xe_tile *tile;
> - /** @vmas: List of VMAs for this BO */
> - struct list_head vmas;
> /** @placements: valid placements for this BO */
> struct ttm_place placements[XE_BO_MAX_PLACEMENTS];
> /** @placement: current placement for this BO */
> diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
> index d1e06c913260..ce8d9e9d1b61 100644
> --- a/drivers/gpu/drm/xe/xe_pt.c
> +++ b/drivers/gpu/drm/xe/xe_pt.c
> @@ -265,7 +265,7 @@ void xe_pt_destroy(struct xe_pt *pt, u32 flags, struct llist_head *deferred)
> if (!pt)
> return;
>
> - XE_WARN_ON(!list_empty(&pt->bo->vmas));
> + XE_WARN_ON(!list_empty(&pt->bo->ttm.base.gpuva.list));
> xe_bo_unpin(pt->bo);
> xe_bo_put_deferred(pt->bo, deferred);
--
Jani Nikula, Intel
prev parent reply other threads:[~2023-09-27 12:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 17:26 [Intel-xe] [PATCH v3] drm/xe: Reinstate pipelined fence enable_signaling Thomas Hellström
2023-09-15 17:29 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Reinstate pipelined fence enable_signaling (rev3) Patchwork
2023-09-15 17:29 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-15 17:30 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-15 17:37 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-15 17:38 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-15 17:39 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-15 18:11 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-09-16 6:56 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Reinstate pipelined fence enable_signaling (rev4) Patchwork
2023-09-16 6:56 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-16 6:57 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-16 7:04 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-16 7:05 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-16 7:06 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-16 7:38 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-09-27 12:17 ` Jani Nikula [this message]
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=87r0mjkdyo.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=thomas.hellstrom@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