All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <sashiko-reviews@lists.linux.dev>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v5 17/25] drm/xe: Add device flag to enable PT mirroring across tiles
Date: Thu, 3 Sep 2026 21:10:14 -0700	[thread overview]
Message-ID: <appEprATsO8O4lEU@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20260904024347.D0DC81F000E9@smtp.kernel.org>

On Fri, Sep 04, 2026 at 02:43:47AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [High] Unused page tables and scratch buffers are incorrectly allocated for secondary tiles when PT mirroring is disabled, wasting VRAM, and migration VMs are forced to use remote page tables.
> - [Medium] Memory leak of page reclaim entries (`prl->entries`) on error paths or when TLB invalidation is bypassed for tiles with disabled page table mirroring.
> --
> 
> commit 38fe6ff118093de1244d8bbcc84d59616c09c17c
> Author: Matthew Brost <matthew.brost@intel.com>
> 
> drm/xe: Add device flag to enable PT mirroring across tiles
> 
> This commit introduces a device flag to enable or disable page-table
> mirroring across tiles for memory-bandwidth reasons. The flag defaults
> to the existing behavior on PVC but allows flexibility for other devices.
> 
> Link: https://patch.msgid.link/20260228013501.106680-18-matthew.brost@intel.com
> 
> > diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
> > index 05bbac6c2632e..bf2cdef44179d 100644
> > --- a/drivers/gpu/drm/xe/xe_pt.c
> > +++ b/drivers/gpu/drm/xe/xe_pt.c
> [ ... ]
> > @@ -2541,9 +2552,21 @@ int xe_pt_update_ops_prepare(struct xe_device *xe, struct xe_vma_ops *vops)
> >  	int id, err;
> >  
> >  	for_each_tile(tile, xe, id) {
> > +		struct xe_vm_pgtable_update_ops *pt_update_ops =
> > +			&vops->pt_update_ops[id];
> > +
> >  		if (!vops->pt_update_ops[id].num_ops)
> >  			continue;
> >  
> > +		if (pt_mirroring_disabled_for_tile(vops->vm, id)) {
> > +			struct xe_page_reclaim_list *prl = &pt_update_ops->prl;
> > +
> > +			/* Transfer root PT update ops PRL to current */
> > +			*prl = vops->pt_update_ops[0].prl;
> > +			xe_page_reclaim_entries_get(prl->entries);
> > +			continue;
> > +		}
> > +
> >  		err = __xe_pt_update_ops_prepare(tile, vops);
> >  		if (err)
> >  			return err;
> [ ... ]
> > @@ -2924,6 +2953,9 @@ void xe_pt_update_ops_fini(struct xe_device *xe, struct xe_vma_ops *vops)
> >  		if (!pt_update_ops->num_ops)
> >  			continue;
> >  
> > +		if (pt_mirroring_disabled_for_tile(vops->vm, id))
> > +			continue;
> > +
> >  		xe_page_reclaim_entries_put(pt_update_ops->prl.entries);
> 
> [Severity: Medium]
> Does this skip releasing the page reclaim entries for secondary tiles?
> 
> When PT mirroring is disabled, xe_pt_update_ops_prepare() takes an extra
> reference to prl->entries for secondary tiles. If the operation succeeds but
> TLB invalidation is bypassed (or if called on cleanup),
> xe_pt_update_ops_fini() is executed. By checking
> pt_mirroring_disabled_for_tile() and continuing, it skips the needed
> xe_page_reclaim_entries_put() call, which can lead to a memory leak.
> 
> >  	}
> >  }
> > @@ -2948,6 +2980,9 @@ void xe_pt_update_ops_abort(struct xe_device *xe, struct xe_vma_ops *vops)
> >  			&vops->pt_update_ops[id];
> >  		int i;
> >  
> > +		if (pt_mirroring_disabled_for_tile(vops->vm, id))
> > +			continue;
> > +
> >  		for (i = pt_update_ops->num_ops - 1; i >= 0; --i) {
> 
> [Severity: Medium]
> Similar to the issue above in xe_pt_update_ops_fini(), does this leak the
> page reclaim entries when an operation is aborted?
> 
> By skipping secondary tiles when mirroring is disabled,
> xe_pt_update_ops_abort() also bypasses xe_pt_update_ops_fini() for those
> tiles, meaning the reference acquired in xe_pt_update_ops_prepare() is
> never put on error paths.
> 

Both of these are correct, pt_mirroring_disabled_for_tile should be
deleted from xe_pt_update_ops_fini.

Matt

> >  			struct xe_vm_pgtable_update_op *pt_op =
> >  				to_pt_op(pt_update_ops, i);
> [ ... ]
> > diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> > index fbfc42afef8b1..795d0ebb10047 100644
> > --- a/drivers/gpu/drm/xe/xe_vm.c
> > +++ b/drivers/gpu/drm/xe/xe_vm.c
> [ ... ]
> > @@ -1738,7 +1748,8 @@ struct xe_vm *xe_vm_create(struct xe_device *xe, u32 flags, struct xe_file *xef)
> >  
> >  		for_each_tile(tile, xe, id) {
> >  			if (flags & XE_VM_FLAG_MIGRATION &&
> > -			    tile->id != XE_VM_FLAG_TILE_ID(flags))
> > +			    tile->id != XE_VM_FLAG_TILE_ID(flags) &&
> > +			    (vm->xe->info.has_pt_mirror || id))
> >  				continue;
> >  
> >  			vm->pt_root[id] = xe_pt_create(vm, tile, xe->info.vm_max_level,
> 
> [Severity: High]
> Does this allocate unused page tables and scratch buffers for secondary tiles
> when PT mirroring is disabled?
> 
> When has_pt_mirror is false, the loop does not skip secondary tiles for
> normal VMs, causing it to unconditionally allocate pt_root structures and
> scratch pages for all of them. 
> 
> Additionally, for migration VMs on secondary tiles, this allocates both
> pt_root[0] and pt_root[tile_id]. Since xe_vm_pt_root() unconditionally
> returns pt_root[0] when mirroring is disabled, this abandons the memory
> allocated for secondary tiles and forces the migration engine to use
> pt_root[0] over the cross-tile interconnect, defeating the locality benefits.
> 
> [ ... ]
> > @@ -5072,3 +5083,21 @@ void xe_vm_remove_exec_queue(struct xe_vm *vm, struct xe_exec_queue *q)
> >  	}
> >  	up_write(&vm->exec_queues.lock);
> >  }
> > +
> > +/**
> > + * xe_vm_pt_root() - Retrieve VM page-table root
> > + * @vm: The VM.
> > + * @tile_id: Tile ID
> > + *
> > + * Retrieve VM page-table root for a tile ID, used to abstract if PT mirroring is
> > + * enabled across tiles.
> > + *
> > + * Return: VM page-table root for a tile ID
> > + */
> > +struct xe_pt *xe_vm_pt_root(struct xe_vm *vm, u8 tile_id)
> > +{
> > +	if (vm->xe->info.has_pt_mirror)
> > +		return vm->pt_root[tile_id];
> > +
> > +	return vm->pt_root[0];
> > +}
> 
> -- 
> Sashiko AI review · https://sashiko.dev/#/patchset/20260904022207.3490018-1-matthew.brost@intel.com?part=17

  reply	other threads:[~2026-09-04  4:10 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04  2:21 [PATCH v5 00/25] CPU binds and ULLS on migration queue Matthew Brost
2026-09-04  2:21 ` [PATCH v5 01/25] drm/xe: Drop struct xe_migrate_pt_update argument from populate/clear vfuns Matthew Brost
2026-09-04  2:21 ` [PATCH v5 02/25] drm/xe: Add xe_migrate_update_pgtables_cpu_execute helper Matthew Brost
2026-09-04  2:37   ` sashiko-bot
2026-09-04  2:21 ` [PATCH v5 03/25] drm/xe: Decouple exec queue idle check from LRC Matthew Brost
2026-09-04  2:21 ` [PATCH v5 04/25] drm/xe: Add job count to GuC exec queue snapshot Matthew Brost
2026-09-04  2:21 ` [PATCH v5 05/25] drm/xe: Update xe_bo_put_deferred arguments to include writeback flag Matthew Brost
2026-09-04  2:44   ` sashiko-bot
2026-09-04  2:21 ` [PATCH v5 06/25] drm/xe: Add XE_BO_FLAG_PUT_VM_ASYNC Matthew Brost
2026-09-04  2:21 ` [PATCH v5 07/25] drm/xe: Update scheduler job layer to support PT jobs Matthew Brost
2026-09-04  2:21 ` [PATCH v5 08/25] drm/xe: Add helpers to access PT ops Matthew Brost
2026-09-04  2:21 ` [PATCH v5 09/25] drm/xe: Add struct xe_pt_job_ops Matthew Brost
2026-09-04  2:48   ` sashiko-bot
2026-09-04  2:21 ` [PATCH v5 10/25] drm/xe: Update GuC submission backend to run PT jobs Matthew Brost
2026-09-04  2:46   ` sashiko-bot
2026-09-04  2:21 ` [PATCH v5 11/25] drm/xe: Store level in struct xe_vm_pgtable_update Matthew Brost
2026-09-04  2:21 ` [PATCH v5 12/25] drm/xe: Don't use migrate exec queue for page fault binds Matthew Brost
2026-09-04  2:21 ` [PATCH v5 13/25] drm/xe: Enable CPU binds for jobs Matthew Brost
2026-09-04  2:51   ` sashiko-bot
2026-09-04  2:21 ` [PATCH v5 14/25] drm/xe: Remove unused arguments from xe_migrate_pt_update_ops Matthew Brost
2026-09-04  2:21 ` [PATCH v5 15/25] drm/xe: Make bind queues operate cross-tile Matthew Brost
2026-09-04  2:21 ` [PATCH v5 16/25] drm/xe: Add CPU bind layer Matthew Brost
2026-09-04  2:21 ` [PATCH v5 17/25] drm/xe: Add device flag to enable PT mirroring across tiles Matthew Brost
2026-09-04  2:43   ` sashiko-bot
2026-09-04  4:10     ` Matthew Brost [this message]
2026-09-04  2:22 ` [PATCH v5 18/25] drm/xe: Add xe_hw_engine_write_ring_tail Matthew Brost
2026-09-04  2:22 ` [PATCH v5 19/25] drm/xe: Add ULLS support to LRC Matthew Brost
2026-09-04  2:22 ` [PATCH v5 20/25] drm/xe: Add ULLS migration job support to migration layer Matthew Brost
2026-09-04  2:44   ` sashiko-bot
2026-09-04  4:11     ` Matthew Brost
2026-09-04  2:22 ` [PATCH v5 21/25] drm/xe: Add ULLS migration job support to ring ops Matthew Brost
2026-09-04  2:22 ` [PATCH v5 22/25] drm/xe: Add ULLS migration job support to GuC submission Matthew Brost
2026-09-04  2:49   ` sashiko-bot
2026-09-04  4:17     ` Matthew Brost
2026-09-04  2:22 ` [PATCH v5 23/25] drm/xe: Enter ULLS for migration jobs upon page fault or SVM prefetch Matthew Brost
2026-09-04  2:22 ` [PATCH v5 24/25] drm/xe: Add modparam to enable / disable ULLS on migrate queue Matthew Brost
2026-09-04  2:22 ` [PATCH v5 25/25] drm/xe: Document ULLS for migration jobs Matthew Brost
2026-09-04  2:29 ` ✗ CI.checkpatch: warning for CPU binds and ULLS on migration queue (rev7) Patchwork
2026-09-04  2:31 ` ✓ CI.KUnit: success " Patchwork
2026-09-04  3:08 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-04 15:21 ` ✗ Xe.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=appEprATsO8O4lEU@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.