Displaying 7 results from an estimated 7 matches for "gf100_vmm_valid".
2022 Dec 28
2
[REGRESSION] GM20B probe fails after commit 2541626cfb79
Hello,
Commit 2541626cfb79 breaks GM20B probe with
the following kernel log:
[ 2.153892] ------------[ cut here ]------------
[ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
[ 2.153916] Modules linked in:
[ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
[ 2.153929] Hardware name: Google Pixel C (DT)
[ 2.153933] Workqueue: events_unbound deferred_probe_work_func
[ 2.153943] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SS...
2023 Jan 15
3
[REGRESSION] GM20B probe fails after commit 2541626cfb79
...at tecnico.ulisboa.pt> wrote:
>
> Hello,
>
> Commit 2541626cfb79 breaks GM20B probe with
> the following kernel log:
>
> [ 2.153892] ------------[ cut here ]------------
> [ 2.153897] WARNING: CPU: 1 PID: 36 at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:273 gf100_vmm_valid+0x2c4/0x390
> [ 2.153916] Modules linked in:
> [ 2.153922] CPU: 1 PID: 36 Comm: kworker/u8:1 Not tainted 6.1.0+ #1
> [ 2.153929] Hardware name: Google Pixel C (DT)
> [ 2.153933] Workqueue: events_unbound deferred_probe_work_func
> [ 2.153943] pstate: 80000005 (Nzcv dai...
2019 May 17
4
drm/nouveau/core/memory: kmemleak 684 new suspected memory leaks
...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:
[<0000000081f2894f>] nvkm_memory_tags_get+0x8e/0x130
[<000000007cd7c0bc>] gf100_vmm_valid+0x196/0x2f0
[<0000000070cc6d67>] nvkm_vmm_map+0xa8/0x360
[<00000000ab678644>] nvkm_vram_map+0x48/0x50
[<00000000d8176378>] nvkm_uvmm_mthd+0x658/0x770
[<00000000463fca5a>] nvkm_ioctl+0xdf/0x177
[<000000000afc4996>] nvif_object_mth...
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 Dec 17
1
[PATCH] drm/nouveau: Add correct turing page kinds
...ma_bits;
diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c b/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c
index ab6424faf84c..6a2d9eb8e1ea 100644
--- a/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c
+++ b/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c
@@ -247,7 +247,7 @@ gf100_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;
@@ -274,8...
2019 May 17
0
drm/nouveau/core/memory: kmemleak 684 new suspected memory leaks
...uot;, 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:
> [<0000000081f2894f>] nvkm_memory_tags_get+0x8e/0x130
> [<000000007cd7c0bc>] gf100_vmm_valid+0x196/0x2f0
> [<0000000070cc6d67>] nvkm_vmm_map+0xa8/0x360
> [<00000000ab678644>] nvkm_vram_map+0x48/0x50
> [<00000000d8176378>] nvkm_uvmm_mthd+0x658/0x770
> [<00000000463fca5a>] nvkm_ioctl+0xdf/0x177
> [<000000000afc...
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