search for: sysmem

Closes: https://gitlab.freedesktop.org/drm/nouveau/-/issues/203 Fixes: 5728d064190e1 ("drm/nouveau/fb: handle sysmem flush page from common code") Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drivers/gpu/drm/nouveau/nvkm/subdev/fb/gf108.c | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/fb/gk104.c | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/fb/gk110.c | 1 + drivers/gpu/drm/nouveau/nvkm/subdev/fb/...

The nvif_object_ioctl() method NVIF_VMM_V0_PFNMAP wasn't correctly setting the hardware specific GPU page table entries for 2MB sized pages. Fix this by adding functions to set and clear PD0 GPU page table entries. Signed-off-by: Ralph Campbell <rcampbell at nvidia.com> --- drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c | 5 +- .../drm/nouveau/nvkm/subdev/mmu/vmmgp100.c | 82

Nouveau currently only supports mapping PAGE_SIZE sized pages of system memory when shared virtual memory (SVM) is enabled. Use the new HMM_PFN_COMPOUND flag that hmm_range_fault() returns to support mapping system memory pages larger than PAGE_SIZE. Signed-off-by: Ralph Campbell <rcampbell at nvidia.com> --- drivers/gpu/drm/nouveau/nouveau_svm.c | 47 ++++++++++++++-----

...since changing the >> 1:1 CPU/GPU page table size assumptions requires a bigger set of changes. >> Rebase to 5.8.0-rc3. >> >> Ralph Campbell (5): >> nouveau/hmm: fault one page at a time >> mm/hmm: add hmm_mapping order >> nouveau: fix mapping 2MB sysmem pages >> nouveau/hmm: support mapping large sysmem pages >> hmm: add tests for HMM_PFN_PMD flag > > Applied to hmm.git. > > I edited the comment for hmm_pfn_to_map_order() and added a function > to compute the field. > > Thanks, > Jason Looks good, than...

...2MB nouveau mappings initially since changing the > 1:1 CPU/GPU page table size assumptions requires a bigger set of changes. > Rebase to 5.8.0-rc3. > > Ralph Campbell (5): > nouveau/hmm: fault one page at a time > mm/hmm: add hmm_mapping order > nouveau: fix mapping 2MB sysmem pages > nouveau/hmm: support mapping large sysmem pages > hmm: add tests for HMM_PFN_PMD flag Applied to hmm.git. I edited the comment for hmm_pfn_to_map_order() and added a function to compute the field. Thanks, Jason

...base); *pfence = NULL; } @@ -307,7 +377,7 @@ struct nouveau_fence * nouveau_fence_ref(struct nouveau_fence *fence) { if (fence) - kref_get(&fence->kref); + fence_get(&fence->base); return fence; } @@ -325,9 +395,7 @@ nouveau_fence_new(struct nouveau_channel *chan, bool sysmem, if (!fence) return -ENOMEM; - INIT_LIST_HEAD(&fence->work); fence->sysmem = sysmem; - kref_init(&fence->kref); ret = nouveau_fence_emit(fence, chan); if (ret) @@ -336,3 +404,85 @@ nouveau_fence_new(struct nouveau_channel *chan, bool sysmem, *pfence = fence; retu...

(Sending it to the correct Nvidia mailing list, sorry for the spam) Hi, When using acceleration with Nouveau on MacBook Pros with an 9400M (NVAC) card, a PFIFO interrupt 0x00400000 is thrown during the initialisation of that card (sometime after PFIFO and PGRAPH initialisation) and the laptop will lockup [1], forcing users to load Nouveau without acceleration. After some investigation, I found

...anges. wined3d: Use the map binding to reload surfaces on color key changes. wined3d: Use the map binding for RGB<->sRGB loads. wined3d: Mark the map binding up to date in texture2d_sub_resource_add_dirty_region. wined3d: Move location flag updating out of surface_init_sysmem. wined3d: Load surfaces into map binding memory on unload. wined3d: Give user memory its own location. wined3d: Use the map binding to optimize sysmem->sysmem blits. wined3d: Make the callers of load_location responsible for allocating sysmem. wined3d: Start to spli...

...motely reasonable. > > If you're having trouble telling, that means it's not :) The error you > pasted is quite odd. Was there anything in the log before those > messages? If there's no channel associated, that means that it's the > background copying between vram and sysmem? Not sure. Don't get too excited yet. In the process of upgrading mesa, I managed to boot 4.5 without noticing. I'll post back later today with actual valid test results. > > Note that with maxwell we have yet to add EXA support to > xf86-video-nouveau, so you're ending up...

...{ + const char *cpu_model = args->cpu_model; + const char *kernel_filename = args->kernel_filename; + const char *kernel_cmdline = args->kernel_cmdline; + const char *initrd_filename = args->initrd_filename; StrongARMState *s; DriveInfo *dinfo; MemoryRegion *sysmem = get_system_memory(); diff --git a/hw/dummy_m68k.c b/hw/dummy_m68k.c index 7cc7a99..f436a0c 100644 --- a/hw/dummy_m68k.c +++ b/hw/dummy_m68k.c @@ -16,11 +16,11 @@ /* Board init. */ -static void dummy_m68k_init(ram_addr_t ram_size, - const char *boot_device, -...

...e. I know it's all very obvious to the people that write the code, but for others it's less obvious. - I think buffer object untiling should happen in userspace, which will also allow some nice optimizations that EXA does (using damage to selectively copy and such). - The WIP patch contains sysmem pixmaps, i fixed this for git xserver (and nominated it for 1.6), but expect older versions to blow up due to NULL'ing of devPrivate.ptr. (http://cgit.freedesktop.org/xorg/xserver/commit/?id=3534a5e5d9c5af85149c799f324257f89507fa23) Consider the patches hints, and don't blindly apply them....

...LER_DLL to d3dcompiler_47.dll. Julian Rüger (1): po: Update German translation. Józef Kucia (14): d3d8: Upload vertex buffer range relative to base vertex index. d3d9: Upload vertex buffer range relative to base vertex index. d3d9/tests: Add test for base vertex index with sysmem vertex buffers. d3d8/tests: Add test for base vertex index with sysmem vertex buffers. ntoskrnl.exe: Fix service handle leak in ZwLoadDriver() (Coverity). ddraw/tests: Add tests for attaching depth buffers of different sizes. ddraw/tests: Fix compilation on systems that don&...

...Ben Skeggs. Only add support for 2MB nouveau mappings initially since changing the 1:1 CPU/GPU page table size assumptions requires a bigger set of changes. Rebase to 5.8.0-rc3. Ralph Campbell (5): nouveau/hmm: fault one page at a time mm/hmm: add hmm_mapping order nouveau: fix mapping 2MB sysmem pages nouveau/hmm: support mapping large sysmem pages hmm: add tests for HMM_PFN_PMD flag drivers/gpu/drm/nouveau/nouveau_svm.c | 236 ++++++++---------- drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c | 5 +- .../drm/nouveau/nvkm/subdev/mmu/vmmgp100.c | 82 ++++++ include/linux/h...

...to TRACE. wnaspi32: Call ASPI_GetNumControllers() only once. wnaspi32: Do the command dumping only after device has been verified. wnaspi32: Fix Controller -> H/C mapping. wnaspi32: Fix controller number validation. Stefan D?singer (58): wined3d: Move drawable->sysmem reading to UpdateLocation. wined3d: Add a comment explaining what LoadLocation does. wined3d: Move sysmem->drawable copying to LoadLocation. wined3d: Move texture loading to LoadLocation. wined3d: Honor pbos when downloading a compressed texture. wined3d: Move textu...

...wo configurations : 1) previous workaround of making nouveau_exa_create_pixmap always fail : performance still acceptable (early fallback) 2) runtime OUT_RELOC failure and fallback : turtle speed (late fallback) The commit that implemented workaround 1 for 32mb vram says : ? ?exa: force the use of sysmem pixmaps on low-mem cards ? ?Very similar effect to forcing MigrationHeuristic "greedy" on classic ? ?EXA. ?Far better than the migration ping-pong that'd occur otherwise I suppose that arch/x86/mm/pageattr.c showing up in the profile, and pixman_blt_mmx taking ages are consequences o...

On Sat, May 28, 2016 at 5:48 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Do you have mesa 11.2 or later? GM20x support was only added in mesa 11.2. > I just upgraded to 11.2. I'm getting errors like this in the log: [ 5383.723240] nouveau 0000:09:00.0: fifo: read fault at 0000011000 engine 07 [PBDMA0] client 06 [HOST] reason 00 [PDE] on channel -1 [007f9ed000 unknown] [

...> > > Each of these should point to at least 32 bytes of otherwise-unused > > FB > > memory, if the poller is enabled. > > > > The proprietary driver enables all three pollers for GPUs that have > > them, when > > memory is not local (i.e., when using a sysmem carveout rather than > > dedicated > > video memory). > > > > I'm not sure why this seems to only be necessary on some systems > > and > > not > > others. > > I didn't meant that it wasn't necessary on other systems, just that > it was...

...propriate. Hans Leidekker (3): mlang: Improve IMLangLineBreakConsole::BreakLineA for the ASCII codepage. advapi32: Perform a case-insensitive match on the credential target name. msi: Fix handling of empty mask edit templates. Henri Verbeet (46): wined3d: Just validate the sysmem location in surface_init(). wined3d: Just use surface_invalidate_location() in surface_map(). wined3d: Get rid of surface_set_dirty(). ddraw: Only reset the device when creating an exclusive mode front buffer in ddraw_surface_create_texture(). ddraw: Don't bother checkin...

...ot/gm200.c @@ -1148,7 +1148,7 @@ gm200_secboot_setup_falcon(struct gm200_secboot *gsb) 0x4 | 0x2); /* Set context */ - if (device->fb->ram) + if (nvkm_memory_target(gsb->inst->memory) == NVKM_MEM_TARGET_VRAM) inst_loc = 0x0; /* FB */ else inst_loc = 0x3; /* Non-coherent sysmem */ -- 2.7.2

...er the performance is remotely reasonable. If you're having trouble telling, that means it's not :) The error you pasted is quite odd. Was there anything in the log before those messages? If there's no channel associated, that means that it's the background copying between vram and sysmem? Not sure. Note that with maxwell we have yet to add EXA support to xf86-video-nouveau, so you're ending up with GLAMOR (and Ben and I disagree on whether EXA support should be added in the first place). There was also an issue that glamor was hitting with nouveau which appears to have dissipa...