search for: cpu_addr_mirror

...t a > > range of the GEM (see the below diff, which is completely untested by > > the way), but I think we'd be fine with this SINGLE_PAGE flag. > > Unless I've misunderstood the intent completely, it looks like Xe also wants > something similar although they call it CPU_ADDR_MIRROR for some reason: > > https://lore.kernel.org/r/20250129195212.745731-9-matthew.brost at intel.com At first glance, it doesn't seem related. The Xe stuff looks more like an alloc-on-fault mechanism. SINGLE_PAGE is about mapping a dummy page repeatedly over a virtual address range so that...

...GEM range, so we can repeat a > range of the GEM (see the below diff, which is completely untested by > the way), but I think we'd be fine with this SINGLE_PAGE flag. Unless I've misunderstood the intent completely, it looks like Xe also wants something similar although they call it CPU_ADDR_MIRROR for some reason: https://lore.kernel.org/r/20250129195212.745731-9-matthew.brost at intel.com Best regards, Liviu > > --->8--- > diff --git a/drivers/gpu/drm/drm_gpuvm.c b/drivers/gpu/drm/drm_gpuvm.c > index f9eb56f24bef..ea61f3ffaddf 100644 > --- a/drivers/gpu/drm/drm_gpuvm.c...

+Akash with whom we've been discussing adding a 'REPEAT' mode to drm_gpuvm/panthor. On Sun, 2 Feb 2025 19:53:47 +0100 Danilo Krummrich <dakr at kernel.org> wrote: > Hi Lina, > > On Sun, Feb 02, 2025 at 10:34:49PM +0900, Asahi Lina wrote: > > Some hardware requires dummy page mappings to efficiently implement > > Vulkan sparse features. These mappings