Lines Matching +full:gpu +full:- +full:id
2 GPU Debugging
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
14 the GPU.
20 If you see a GPU page fault in the kernel log, you can decode it to figure
26 …[gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32777, for process glxinfo pid 2424 t…
29 Faulty UTCL2 client ID: TCP (0x8)
38 memory hub used for multi-media and sdma on some chips.
41 caused by the kernel driver or firmware. If the vmid is non-0, it is generally
43 process id. If the process is active when the fault happens, the process
46 The GPU virtual address that caused the fault comes next.
48 The client ID indicates the GPU block that caused the fault.
51 - CB/DB: The color/depth backend of the graphics pipe
52 - CPF: Command Processor Frontend
53 - CPC: Command Processor Compute
54 - CPG: Command Processor Graphics
55 - TCP/SQC/SQG: Shaders
56 - SDMA: SDMA engines
57 - VCN: Video encode/decode engines
58 - JPEG: JPEG engines
62 - bit 0: the PTE was not valid
63 - bit 1: the PTE read bit was not set
64 - bit 2: the PTE write bit was not set
65 - bit 3: the PTE execute bit was not set
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
72 descriptor state to determine what caused the GPU page fault.
78 GPU debugging and diagnostics tool. Please see the umr