[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260106171047.766d826f@gandalf.local.home>
Date: Tue, 6 Jan 2026 17:10:47 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Xiang Gao <gxxa03070307@...il.com>
Cc: sumit.semwal@...aro.org, christian.koenig@....com, mhiramat@...nel.org,
linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, mathieu.desnoyers@...icios.com,
dhowells@...hat.com, kuba@...nel.org, brauner@...nel.org,
akpm@...ux-foundation.org, linux-trace-kernel@...r.kernel.org, gaoxiang17
<gaoxiang17@...omi.com>
Subject: Re: [PATCH v12] dma-buf: add some tracepoints to debug.
On Mon, 29 Dec 2025 11:15:47 +0800
Xiang Gao <gxxa03070307@...il.com> wrote:
> From: gaoxiang17 <gaoxiang17@...omi.com>
>
> 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@...omi.com>
From a tracing POV:
Reviewed-by: Steven Rostedt (Google) <rostedt@...dmis.org>
-- Steve
Powered by blists - more mailing lists