intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Alistair Popple <apopple@nvidia.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	himal.prasad.ghimiray@intel.com, airlied@gmail.com,
	"Simona Vetter" <simona.vetter@ffwll.ch>,
	felix.kuehling@amd.com, "Matthew Brost" <matthew.brost@intel.com>,
	"Christian König" <christian.koenig@amd.com>,
	dakr@kernel.org, "Mrozek, Michal" <michal.mrozek@intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>
Subject: Re: [PATCH v2 00/17] Dynamic drm_pagemaps and Initial multi-device SVM
Date: Tue, 18 Nov 2025 10:31:41 +0100	[thread overview]
Message-ID: <bd0d03a73dc831ea206dcb5d4a9d912e96729861.camel@linux.intel.com> (raw)
In-Reply-To: <gdveezxmqazqdyuyy6kpca7kfppxkackmcms6xrfcya2acqzat@jd2yjghp5bcm>

On Tue, 2025-11-18 at 17:15 +1100, Alistair Popple wrote:
> On 2025-11-12 at 03:43 +1100, Thomas Hellström
> <thomas.hellstrom@linux.intel.com> wrote...
> > This series aims at providing an initial implementation of multi-
> > device
> > SVM, where communitcation with peers (migration and direct
> > execution out
> > of peer memory) uses some form of fast interconnect. In this series
> > we're using pcie p2p.
> > 
> > In a multi-device environment, the struct pages for device-private
> > memory
> > (the dev_pagemap) may take up a significant amount of system
> > memory. We
> > therefore want to provide a means of revoking / removing the
> > dev_pagemaps
> > not in use. In particular when a device is offlined, we want to
> > block
> > migrating *to* the device memory and migrate data already existing
> > in the
> > devices memory to system. The dev_pagemap then becomes unused and
> > can be
> > removed.
> > 
> > Removing and setting up a large dev_pagemap is also quite time-
> > consuming,
> > so removal of unused dev_pagemaps only happens on system memory
> > pressure
> > using a shrinker.
> 
> Agree it is quite time-consuming, we have run into this problem as
> well
> including with the pcie p2p dma pages. On the mm side I've started
> looking
> at if/how we can remove the need for struct pages at all for
> supporting this.
> Doesn't help you at all now of course, but hopefully one day we can
> avoid the
> need for this. I will be discussing this at LPC if you happen to be
> there.

Yeah that sounds great. Will not be at LPC in person but will make sure
to join remotely.

Thanks,
Thomas




> 
>  - Alistair
> 
> > Patch 1 is a small debug printout fix.
> > Patches 2-7 deals with dynamic drm_pagemaps as described above.
> > Patches 8-12 adds infrastructure to handle remote drm_pagemaps with
> > fast interconnects.
> > Patch 13 extends the xe madvise() UAPI to handle remote
> > drm_pagemaps.
> > Patch 14 adds a pcie-p2p dma SVM interconnect to the xe driver.
> > Patch 15 adds some SVM-related debug printouts for xe.
> > Patch 16 adds direct interconnect migration.
> > Patch 17 adds some documentation.
> > 
> > What's still missing is implementation of migration policies.
> > That will be implemented in follow-up series. 
> > 
> > v2:
> > - Address review comments from Matt Brost.
> > - Fix compilation issues reported by automated testing
> > - Add patch 1, 17.
> > - What's now patch 16 was extended to support p2p migration.
> > 
> > Thomas Hellström (17):
> >   drm/xe/svm: Fix a debug printout
> >   drm/pagemap, drm/xe: Add refcounting to struct drm_pagemap
> >   drm/pagemap: Add a refcounted drm_pagemap backpointer to struct
> >     drm_pagemap_zdd
> >   drm/pagemap, drm/xe: Manage drm_pagemap provider lifetimes
> >   drm/pagemap: Add a drm_pagemap cache and shrinker
> >   drm/xe: Use the drm_pagemap cache and shrinker
> >   drm/pagemap: Remove the drm_pagemap_create() interface
> >   drm/pagemap_util: Add a utility to assign an owner to a set of
> >     interconnected gpus
> >   drm/xe: Use the drm_pagemap_util helper to get a svm pagemap
> > owner
> >   drm/xe: Pass a drm_pagemap pointer around with the memory advise
> >     attributes
> >   drm/xe: Use the vma attibute drm_pagemap to select where to
> > migrate
> >   drm/xe: Simplify madvise_preferred_mem_loc()
> >   drm/xe/uapi: Extend the madvise functionality to support foreign
> >     pagemap placement for svm
> >   drm/xe: Support pcie p2p dma as a fast interconnect
> >   drm/xe/vm: Add a couple of VM debug printouts
> >   drm/pagemap, drm/xe: Support migration over interconnect
> >   drm/xe/svm: Document how xe keeps drm_pagemap references
> > 
> >  drivers/gpu/drm/Makefile             |   3 +-
> >  drivers/gpu/drm/drm_gpusvm.c         |   4 +-
> >  drivers/gpu/drm/drm_pagemap.c        | 354 ++++++++++++---
> >  drivers/gpu/drm/drm_pagemap_util.c   | 568
> > ++++++++++++++++++++++++
> >  drivers/gpu/drm/xe/xe_device.c       |  20 +
> >  drivers/gpu/drm/xe/xe_device.h       |   2 +
> >  drivers/gpu/drm/xe/xe_device_types.h |   5 +
> >  drivers/gpu/drm/xe/xe_svm.c          | 631 ++++++++++++++++++++++-
> > ----
> >  drivers/gpu/drm/xe/xe_svm.h          |  82 +++-
> >  drivers/gpu/drm/xe/xe_tile.c         |  34 +-
> >  drivers/gpu/drm/xe/xe_tile.h         |  21 +
> >  drivers/gpu/drm/xe/xe_userptr.c      |   2 +-
> >  drivers/gpu/drm/xe/xe_vm.c           |  65 ++-
> >  drivers/gpu/drm/xe/xe_vm.h           |   1 +
> >  drivers/gpu/drm/xe/xe_vm_madvise.c   | 106 ++++-
> >  drivers/gpu/drm/xe/xe_vm_types.h     |  21 +-
> >  drivers/gpu/drm/xe/xe_vram_types.h   |  15 +-
> >  include/drm/drm_pagemap.h            |  91 +++-
> >  include/drm/drm_pagemap_util.h       |  92 ++++
> >  include/uapi/drm/xe_drm.h            |  18 +-
> >  20 files changed, 1898 insertions(+), 237 deletions(-)
> >  create mode 100644 drivers/gpu/drm/drm_pagemap_util.c
> >  create mode 100644 include/drm/drm_pagemap_util.h
> > 
> > -- 
> > 2.51.1
> > 


      reply	other threads:[~2025-11-18  9:31 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-11 16:43 [PATCH v2 00/17] Dynamic drm_pagemaps and Initial multi-device SVM Thomas Hellström
2025-11-11 16:43 ` [PATCH v2 01/17] drm/xe/svm: Fix a debug printout Thomas Hellström
2025-11-12  4:29   ` Ghimiray, Himal Prasad
2025-11-11 16:43 ` [PATCH v2 02/17] drm/pagemap, drm/xe: Add refcounting to struct drm_pagemap Thomas Hellström
2025-11-12  6:07   ` Ghimiray, Himal Prasad
2025-11-21 10:19     ` Thomas Hellström
2025-11-11 16:43 ` [PATCH v2 03/17] drm/pagemap: Add a refcounted drm_pagemap backpointer to struct drm_pagemap_zdd Thomas Hellström
2025-11-11 16:43 ` [PATCH v2 04/17] drm/pagemap, drm/xe: Manage drm_pagemap provider lifetimes Thomas Hellström
2025-11-18  0:44   ` Matthew Brost
2025-11-11 16:43 ` [PATCH v2 05/17] drm/pagemap: Add a drm_pagemap cache and shrinker Thomas Hellström
2025-11-19 19:28   ` Matthew Brost
2025-11-11 16:43 ` [PATCH v2 06/17] drm/xe: Use the " Thomas Hellström
2025-11-26  0:22   ` Matthew Brost
2025-11-11 16:43 ` [PATCH v2 07/17] drm/pagemap: Remove the drm_pagemap_create() interface Thomas Hellström
2025-11-11 16:43 ` [PATCH v2 08/17] drm/pagemap_util: Add a utility to assign an owner to a set of interconnected gpus Thomas Hellström
2025-11-11 16:43 ` [PATCH v2 09/17] drm/xe: Use the drm_pagemap_util helper to get a svm pagemap owner Thomas Hellström
2025-11-26  0:55   ` Matthew Brost
2025-11-11 16:44 ` [PATCH v2 10/17] drm/xe: Pass a drm_pagemap pointer around with the memory advise attributes Thomas Hellström
2025-11-26  0:37   ` Matthew Brost
2025-11-11 16:44 ` [PATCH v2 11/17] drm/xe: Use the vma attibute drm_pagemap to select where to migrate Thomas Hellström
2025-11-12  5:22   ` kernel test robot
2025-11-12  7:16   ` kernel test robot
2025-11-13  4:51   ` kernel test robot
2025-11-26  1:09   ` Matthew Brost
2025-11-11 16:44 ` [PATCH v2 12/17] drm/xe: Simplify madvise_preferred_mem_loc() Thomas Hellström
2025-11-11 16:44 ` [PATCH v2 13/17] drm/xe/uapi: Extend the madvise functionality to support foreign pagemap placement for svm Thomas Hellström
2025-11-26  0:43   ` Matthew Brost
2025-11-11 16:44 ` [PATCH v2 14/17] drm/xe: Support pcie p2p dma as a fast interconnect Thomas Hellström
2025-11-26  0:56   ` Matthew Brost
2025-11-11 16:44 ` [PATCH v2 15/17] drm/xe/vm: Add a couple of VM debug printouts Thomas Hellström
2025-11-11 16:44 ` [PATCH v2 16/17] drm/pagemap, drm/xe: Support migration over interconnect Thomas Hellström
2025-11-26 16:32   ` Matthew Brost
2025-11-26 18:52     ` Thomas Hellström
2025-11-11 16:44 ` [PATCH v2 17/17] drm/xe/svm: Document how xe keeps drm_pagemap references Thomas Hellström
2025-11-18  0:49   ` Matthew Brost
2025-11-11 17:07 ` ✗ CI.checkpatch: warning for Dynamic drm_pagemaps and Initial multi-device SVM (rev2) Patchwork
2025-11-11 17:08 ` ✓ CI.KUnit: success " Patchwork
2025-11-11 17:45 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-12  2:53 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-18  6:15 ` [PATCH v2 00/17] Dynamic drm_pagemaps and Initial multi-device SVM Alistair Popple
2025-11-18  9:31   ` Thomas Hellström [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=bd0d03a73dc831ea206dcb5d4a9d912e96729861.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=apopple@nvidia.com \
    --cc=christian.koenig@amd.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felix.kuehling@amd.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=matthew.brost@intel.com \
    --cc=michal.mrozek@intel.com \
    --cc=simona.vetter@ffwll.ch \
    /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;
as well as URLs for NNTP newsgroup(s).