accel/habanalabs: don't trace cpu accessible dma alloc/free

Browse source

The cpu accessible dma allocations use the gen_pool api which actually
does not allocate new memory from the system but manages memory already
allocated before. When tracing this together with real dma
allocation/free it cause confusing logs like a '0' dma address and
a cpu address appearing twice etc.

Signed-off-by: Dafna Hirschfeld <dhirschfeld@habana.ai>
Reviewed-by: Oded Gabbay <ogabbay@kernel.org>
Signed-off-by: Oded Gabbay <ogabbay@kernel.org>
Reviewed-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>

...

This commit is contained in:

Dafna Hirschfeld 2023-02-01 18:46:10 +02:00 • committed by Oded Gabbay

parent 1d0f9ad7ce

commit 4a2e9d11fc

2 changed files with 12 additions and 29 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

29

drivers/accel/habanalabs/common/device.c

View file

12

drivers/accel/habanalabs/common/habanalabs.h

View file