From: Matthew Brost <matthew.brost@intel.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: <intel-xe@lists.freedesktop.org>, <linux-media@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<thomas.hellstrom@linux.intel.com>, <sumit.semwal@linaro.org>,
<daniel@ffwll.ch>
Subject: Re: [PATCH v3 2/2] drm/xe: Use dma-fence array for media GT TLB invalidations in PT code
Date: Fri, 23 Aug 2024 15:38:54 +0000 [thread overview]
Message-ID: <ZsitDqXwHtIBC5ul@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <2657940b-90b3-4abc-9f56-f6c6b70563ec@amd.com>
On Fri, Aug 23, 2024 at 08:40:40AM +0200, Christian König wrote:
> Am 23.08.24 um 06:54 schrieb Matthew Brost:
> > Using a chain fence is problematic as these cannot be installed in
> > timeout drm sync objects. Use a dma-fence-array instead at the cost of
> > an extra failure point.
>
> Mhm, IIRC we converted chain objects into dma-fence-arrays while installing
> them into a timeline.
>
> Doesn't that work any more?
>
Thanks for the quick feedback.
As is, installing a dma-fence-chain into a timeline sync doesn't work.
The 'fence' returned from 'xe_pt_update_ops_run' is installed here [1]
as the 'fence' argument. This blows up here [2] [3]. It does suggest in
[3] to use a dma-fence-array which is what I'm doing.
The issue with using a dma-fence array as is it adds another failure
point if dma_fence_array_create is used as is after collecting multiple
fences from TLB invalidations. Also we have lock in xe_pt_update_ops_run
which is in the path reclaim so calling dma_fence_array_create isn't
allowed under that lock.
I suppose we could drop that lock and directly wait TLB invalidation
fences if dma_fence_array_create fails but to me it makes more sense to
prealloc the dma-fence-array and populate it later. Saw your response to
my first patch about how this could be problematic, a little confused on
that so responding there too.
Matt
[1] https://elixir.bootlin.com/linux/v6.10.6/source/drivers/gpu/drm/xe/xe_sync.c#L233
[2] https://elixir.bootlin.com/linux/v6.10.6/source/drivers/gpu/drm/drm_syncobj.c#L349
[3] https://elixir.bootlin.com/linux/v6.10.6/source/drivers/dma-buf/dma-fence-chain.c#L275
> Regards,
> Christian.
>
> >
> > Also fixup reserve fence count to include media GT invalidation fence.
> >
> > v2:
> > - Fix reserve fence count (Casey Bowman)
> > v3:
> > - Prealloc dma fence array (CI)
> >
> > Fixes: 40520283e0fd ("drm/xe: Invalidate media_gt TLBs in PT code")
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_pt.c | 34 ++++++++++++++++++++++++----------
> > 1 file changed, 24 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
> > index 6c6714af3d5d..2e35444a85b0 100644
> > --- a/drivers/gpu/drm/xe/xe_pt.c
> > +++ b/drivers/gpu/drm/xe/xe_pt.c
> > @@ -3,7 +3,7 @@
> > * Copyright © 2022 Intel Corporation
> > */
> > -#include <linux/dma-fence-chain.h>
> > +#include <linux/dma-fence-array.h>
> > #include "xe_pt.h"
> > @@ -1629,9 +1629,11 @@ xe_pt_update_ops_rfence_interval(struct xe_vm_pgtable_update_ops *pt_update_ops,
> > static int vma_reserve_fences(struct xe_device *xe, struct xe_vma *vma)
> > {
> > + int shift = xe_device_get_root_tile(xe)->media_gt ? 1 : 0;
> > +
> > if (!xe_vma_has_no_bo(vma) && !xe_vma_bo(vma)->vm)
> > return dma_resv_reserve_fences(xe_vma_bo(vma)->ttm.base.resv,
> > - xe->info.tile_count);
> > + xe->info.tile_count << shift);
> > return 0;
> > }
> > @@ -1818,6 +1820,7 @@ int xe_pt_update_ops_prepare(struct xe_tile *tile, struct xe_vma_ops *vops)
> > struct xe_vm_pgtable_update_ops *pt_update_ops =
> > &vops->pt_update_ops[tile->id];
> > struct xe_vma_op *op;
> > + int shift = tile->media_gt ? 1 : 0;
> > int err;
> > lockdep_assert_held(&vops->vm->lock);
> > @@ -1826,7 +1829,7 @@ int xe_pt_update_ops_prepare(struct xe_tile *tile, struct xe_vma_ops *vops)
> > xe_pt_update_ops_init(pt_update_ops);
> > err = dma_resv_reserve_fences(xe_vm_resv(vops->vm),
> > - tile_to_xe(tile)->info.tile_count);
> > + tile_to_xe(tile)->info.tile_count << shift);
> > if (err)
> > return err;
> > @@ -1983,7 +1986,8 @@ xe_pt_update_ops_run(struct xe_tile *tile, struct xe_vma_ops *vops)
> > &vops->pt_update_ops[tile->id];
> > struct dma_fence *fence;
> > struct invalidation_fence *ifence = NULL, *mfence = NULL;
> > - struct dma_fence_chain *chain_fence = NULL;
> > + struct dma_fence **fences = NULL;
> > + struct dma_fence_array *cf = NULL;
> > struct xe_range_fence *rfence;
> > struct xe_vma_op *op;
> > int err = 0, i;
> > @@ -2022,8 +2026,13 @@ xe_pt_update_ops_run(struct xe_tile *tile, struct xe_vma_ops *vops)
> > err = -ENOMEM;
> > goto free_ifence;
> > }
> > - chain_fence = dma_fence_chain_alloc();
> > - if (!chain_fence) {
> > + fences = kmalloc_array(2, sizeof(*fences), GFP_KERNEL);
> > + if (!fences) {
> > + err = -ENOMEM;
> > + goto free_ifence;
> > + }
> > + cf = dma_fence_array_alloc(2);
> > + if (!cf) {
> > err = -ENOMEM;
> > goto free_ifence;
> > }
> > @@ -2068,9 +2077,13 @@ xe_pt_update_ops_run(struct xe_tile *tile, struct xe_vma_ops *vops)
> > invalidation_fence_init(tile->media_gt, mfence, fence,
> > pt_update_ops->start,
> > pt_update_ops->last, vm->usm.asid);
> > - dma_fence_chain_init(chain_fence, &ifence->base.base,
> > - &mfence->base.base, 0);
> > - fence = &chain_fence->base;
> > + fences[0] = &ifence->base.base;
> > + fences[1] = &mfence->base.base;
> > + dma_fence_array_arm(cf, 2, fences,
> > + vm->composite_fence_ctx,
> > + vm->composite_fence_seqno++,
> > + false);
> > + fence = &cf->base;
> > } else {
> > fence = &ifence->base.base;
> > }
> > @@ -2108,7 +2121,8 @@ xe_pt_update_ops_run(struct xe_tile *tile, struct xe_vma_ops *vops)
> > free_rfence:
> > kfree(rfence);
> > free_ifence:
> > - dma_fence_chain_free(chain_fence);
> > + kfree(cf);
> > + kfree(fences);
> > kfree(mfence);
> > kfree(ifence);
> > kill_vm_tile1:
>
next prev parent reply other threads:[~2024-08-23 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 4:54 [PATCH v3 0/2] Replace dma-fence chain with dma-fence array for media GT TLB invalidation Matthew Brost
2024-08-23 4:54 ` [PATCH v3 1/2] dma-buf: Split out dma fence array create into alloc and arm functions Matthew Brost
2024-08-23 6:37 ` Christian König
2024-08-23 15:46 ` Matthew Brost
2024-08-27 17:15 ` Daniel Vetter
2024-08-23 4:54 ` [PATCH v3 2/2] drm/xe: Use dma-fence array for media GT TLB invalidations in PT code Matthew Brost
2024-08-23 6:40 ` Christian König
2024-08-23 15:38 ` Matthew Brost [this message]
2024-08-26 7:43 ` Christian König
2024-08-26 8:45 ` Matthew Brost
2024-08-23 5:04 ` ✓ CI.Patch_applied: success for Replace dma-fence chain with dma-fence array for media GT TLB invalidation Patchwork
2024-08-23 5:04 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-23 5:05 ` ✓ CI.KUnit: success " Patchwork
2024-08-23 5:17 ` ✓ CI.Build: " Patchwork
2024-08-23 5:19 ` ✓ CI.Hooks: " Patchwork
2024-08-23 5:21 ` ✗ CI.checksparse: warning " Patchwork
2024-08-23 5:45 ` ✓ CI.BAT: success " Patchwork
2024-08-23 13:32 ` ✗ CI.FULL: failure " 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=ZsitDqXwHtIBC5ul@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.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