Displaying 6 results from an estimated 6 matches for "gp100_vmm_valid".
Did you mean:
gf100_vmm_valid
2019 Dec 17
1
[PATCH] drm/nouveau: Add correct turing page kinds
...VAL;
}
diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgp100.c b/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgp100.c
index b4f519768d5e..d86287565542 100644
--- a/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgp100.c
+++ b/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgp100.c
@@ -320,7 +320,7 @@ gp100_vmm_valid(struct nvkm_vmm *vmm, void *argv, u32 argc,
} *args = argv;
struct nvkm_device *device = vmm->mmu->subdev.device;
struct nvkm_memory *memory = map->memory;
- u8 kind, priv, ro, vol;
+ u8 kind, kind_inv, priv, ro, vol;
int kindn, aper, ret = -ENOSYS;
const u8 *kindm;
@@ -347,8...
2019 Oct 09
3
[Bug 111940] New: frequent timeout warnings during normal operation
...0a006 CR4:
00000000003606e0
[410260.351232] Call Trace:
[410260.351312] nv50_instobj_release+0x2f/0xc0 [nouveau]
[410260.351389] nvkm_vmm_iter.constprop.0+0x2bc/0x810 [nouveau]
[410260.351397] ? do_invalid_op+0x37/0x40
[410260.351475] ? gp100_vmm_pgt_dma+0x200/0x200 [nouveau]
[410260.351563] ? gp100_vmm_valid+0xf8/0x290 [nouveau]
[410260.351661] nvkm_vmm_map+0x136/0x360 [nouveau]
[410260.351678] ? gp100_vmm_pgt_dma+0x200/0x200 [nouveau]
[410260.351678] nvkm_vram_map+0x56/0x80 [nouveau]
[410260.351678] nvkm_uvmm_mthd+0x66a/0x780 [nouveau]
[410260.351678] nvkm_ioctl+0xde/0x180 [nouveau]
[410260.35167...
2019 Sep 16
9
[PATCH 0/6] drm/nouveau: Preparatory work for GV11B support
From: Thierry Reding <treding at nvidia.com>
Hi Ben,
these are a couple of patches that are in preparation for adding GV11B
support. The fundamental issue that these are trying to solve is that
the GV11B is the first Tegra incarnation of the GPU where the aperture
really matters. All prior generations would accept any of them.
For dGPUs we usually allocate memory in VRAM, so the default
2019 May 17
0
drm/nouveau/core/memory: kmemleak 684 new suspected memory leaks
On (05/17/19 15:13), Sergey Senozhatsky wrote:
> ... but most likely it's utterly wrong.
>
JFI, I removed kmemleak annotation and added the following
thing:
@@ -360,6 +360,7 @@ gp100_vmm_valid(struct nvkm_vmm *vmm, void *argv, u32 argc,
return -EINVAL;
}
+ kfree(map->tags);
ret = nvkm_memory_tags_get(memory, device, tags,
nvkm_ltc_tags_clear,...
2019 May 17
4
drm/nouveau/core/memory: kmemleak 684 new suspected memory leaks
Hello,
5.1.0-next-20190517
I'm looking at quite a lot of kmemleak reports coming from
drm/nouveau/core/memory, all of which are:
unreferenced object 0xffff8deec27c4ac0 (size 16):
comm "Web Content", pid 5309, jiffies 4309675011 (age 68.076s)
hex dump (first 16 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
2019 Sep 16
15
[PATCH 00/11] drm/nouveau: Enable GP10B by default
From: Thierry Reding <treding at nvidia.com>
Hi,
the GPU on Jetson TX2 (GP10B) does not work properly on all devices. Why
exactly is not clear, but there are slight differences between the SKUs
that were tested. It turns out that the biggest issue is that on some
devices (e.g. the one that I have), pulsing the GPU reset twice as is
done in the current code (once as part of the power-ungate