Files
linux/include/trace/events
gaoxiang17 281a226314 dma-buf: add some tracepoints to debug.
Since we can only inspect dmabuf by iterating over process FDs or the
dmabuf_list, we need to add our own tracepoints to track its status in
real time in production.

For example:
   binder:3016_1-3102    [006] ...1.   255.126521: dma_buf_export: exp_name=qcom,system size=12685312 ino=2738
   binder:3016_1-3102    [006] ...1.   255.126528: dma_buf_fd: exp_name=qcom,system size=12685312 ino=2738 fd=8
   binder:3016_1-3102    [006] ...1.   255.126642: dma_buf_mmap_internal: exp_name=qcom,system size=28672 ino=2739
     kworker/6:1-86      [006] ...1.   255.127194: dma_buf_put: exp_name=qcom,system size=12685312 ino=2738
    RenderThread-9293    [006] ...1.   316.618179: dma_buf_get: exp_name=qcom,system size=12771328 ino=2762 fd=176
    RenderThread-9293    [006] ...1.   316.618195: dma_buf_dynamic_attach: exp_name=qcom,system size=12771328 ino=2762 attachment:ffffff880a18dd00 is_dynamic=0 dev_name=kgsl-3d0
    RenderThread-9293    [006] ...1.   318.878220: dma_buf_detach: exp_name=qcom,system size=12771328 ino=2762 attachment:ffffff880a18dd00 is_dynamic=0 dev_name=kgsl-3d0

Signed-off-by: Xiang Gao <gaoxiang17@xiaomi.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Link: https://lore.kernel.org/r/20251218062853.819744-1-gxxa03070307@gmail.com
Signed-off-by: Christian König <christian.koenig@amd.com>
2025-12-18 11:21:51 +01:00
..
2024-11-22 11:43:27 -07:00
2025-11-26 17:13:33 -05:00
2025-08-26 17:34:31 -07:00
2024-05-08 10:39:26 +01:00
2023-12-29 11:58:27 -08:00
2023-07-17 08:18:17 -06:00
2024-11-11 00:26:46 -08:00
2025-07-09 22:41:55 -07:00
2024-05-14 07:22:35 -06:00
2024-09-11 20:44:31 -07:00
2025-09-13 16:55:07 -07:00
2025-11-14 17:05:53 +01:00
2024-09-28 15:13:56 +02:00
2025-09-21 14:22:28 -07:00
2025-11-04 08:32:14 +01:00
2024-06-19 12:44:22 +01:00
2025-04-11 18:58:10 -07:00
2025-10-27 11:10:50 +00:00
2025-07-14 12:46:48 -04:00
2023-07-17 08:18:17 -06:00
2023-09-19 07:04:49 +02:00