Lines Matching +full:0 +full:a

8 To aid in debugging GPU virtual memory related problems, the driver supports a
11 `vm_fault_stop` - If non-0, halt the GPU memory controller on a GPU page fault.
13 `vm_update_mode` - If non-0, use the CPU to update GPU page tables rather than
17 Decoding a GPUVM Page Fault
20 If you see a GPU page fault in the kernel log, you can decode it to figure
21 out what is going wrong in your application.  A page fault in your kernel
26 …[gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32777, for process glxinfo pid 2424 t…
27    in page starting at address 0x0000800102800000 from IH client 0x1b (UTCL2)
28  VM_L2_PROTECTION_FAULT_STATUS:0x00301030
29  	Faulty UTCL2 client ID: TCP (0x8)
30  	MORE_FAULTS: 0x0
31  	WALKER_ERROR: 0x0
32  	PERMISSION_FAULTS: 0x3
33  	MAPPING_ERROR: 0x0
34  	RW: 0x0
40 Next you have the vmid and pasid.  If the vmid is 0, this fault was likely
41 caused by the kernel driver or firmware.  If the vmid is non-0, it is generally
42 a fault in a user application.  The pasid is used to link a vmid to a system
62 - bit 0: the PTE was not valid
67 Finally, RW, indicates whether the access was a read (0) or a write (1).
69 In the example above, a shader (cliend id = TCP) generated a read (RW = 0x0) to
70 an invalid page (PERMISSION_FAULTS = 0x3) at GPU virtual address
71 0x0000800102800000.  The user can then inspect their shader code and resource
77 `umr <https://gitlab.freedesktop.org/tomstdenis/umr>`_ is a general purpose