On Wed, Jun 18, 2025 at 05:26:48PM +0200, Thomas Hellström wrote:
> Hi, Matt,
>
> On Wed, 2025-06-18 at 08:26 -0700, Matthew Brost wrote:
> > On Wed, Jun 18, 2025 at 04:21:22PM +0530, Ghimiray, Himal Prasad
> > wrote:
> > >
> > >
> > > On 18-06-2025 14:56, Thomas Hellström wrote:
> > > > From: M
Hi, Matt,
On Wed, 2025-06-18 at 08:26 -0700, Matthew Brost wrote:
> On Wed, Jun 18, 2025 at 04:21:22PM +0530, Ghimiray, Himal Prasad
> wrote:
> >
> >
> > On 18-06-2025 14:56, Thomas Hellström wrote:
> > > From: Matthew Brost
> > >
> > > The migration functionality and track-keeping of per-page
On Wed, Jun 18, 2025 at 04:21:22PM +0530, Ghimiray, Himal Prasad wrote:
>
>
> On 18-06-2025 14:56, Thomas Hellström wrote:
> > From: Matthew Brost
> >
> > The migration functionality and track-keeping of per-pagemap VRAM
> > mapped to the CPU mm is not per GPU_vm, but rather per pagemap.
> > Th
On 18-06-2025 14:56, Thomas Hellström wrote:
From: Matthew Brost
The migration functionality and track-keeping of per-pagemap VRAM
mapped to the CPU mm is not per GPU_vm, but rather per pagemap.
This is also reflected by the functions not needing the drm_gpusvm
structures. So move to drm_pag
From: Matthew Brost
The migration functionality and track-keeping of per-pagemap VRAM
mapped to the CPU mm is not per GPU_vm, but rather per pagemap.
This is also reflected by the functions not needing the drm_gpusvm
structures. So move to drm_pagemap.
With this, drm_gpusvm shouldn't really acce
