On Tue, Dec 16, 2025 at 4:44 PM Christian König <[email protected]> wrote: > > On 12/16/25 07:39, Xiang Gao wrote: > > From: gaoxiang17 <[email protected]> > > > > 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 <[email protected]> > > Reviewed-by: Christian König <[email protected]> > > Going to push this to drm-misc-next today unless somebody has some last > minute objections.
No objection, but I would strongly suggest Xiang include a diff description next time, after the changelog for each new version. I recall clearly commenting on both changelog refinement and the DMA_BUF_TRACE() macro [1]. It would be better to mention similar things for each new version next time :-) [1] https://lore.kernel.org/lkml/CAGsJ_4y0zc_nh2q=w4ur04vtvecf6l7+hgafznhul8bywby...@mail.gmail.com/ Thanks Barry
