diff options
| author | Sean Anderson <[email protected]> | 2024-10-18 15:00:36 +0000 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2024-10-29 07:54:03 +0000 |
| commit | c4484ab86ee00f2d9236e2851621ea02c105f4cc (patch) | |
| tree | e07e81072bdba4a275f3caa6459e7975fd3cc0b2 /lib/xarray.c | |
| parent | dma-mapping: trace dma_alloc/free direction (diff) | |
| download | kernel-c4484ab86ee00f2d9236e2851621ea02c105f4cc.tar.gz kernel-c4484ab86ee00f2d9236e2851621ea02c105f4cc.zip | |
dma-mapping: use trace_dma_alloc for dma_alloc* instead of using trace_dma_map
In some cases, we use trace_dma_map to trace dma_alloc* functions. This
generally follows dma_debug. However, this does not record all of the
relevant information for allocations, such as GFP flags. Create new
dma_alloc tracepoints for these functions. Note that while
dma_alloc_noncontiguous may allocate discontiguous pages (from the CPU's
point of view), the device will only see one contiguous mapping.
Therefore, we just need to trace dma_addr and size.
Signed-off-by: Sean Anderson <[email protected]>
Reviewed-by: Steven Rostedt (Google) <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'lib/xarray.c')
0 files changed, 0 insertions, 0 deletions