From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: matthew.auld@intel.com, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
simona.vetter@ffwll.ch, michael.j.ruhl@intel.com
Subject: [PATCH 2/2] dma-buf: enable DMABUF_DEBUG by default on DEBUG kernels
Date: Fri, 5 Dec 2025 14:06:04 +0100 [thread overview]
Message-ID: <20251205130604.1582-2-christian.koenig@amd.com> (raw)
In-Reply-To: <20251205130604.1582-1-christian.koenig@amd.com>
The overhead of enforcing the DMA-buf rules for importers is now so low
that it save to enable it by default on DEBUG kernels.
This will hopefully result in fixing more issues in importers.
Signed-off-by: Christian König <christian.koenig@amd.com>
---
drivers/dma-buf/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma-buf/Kconfig b/drivers/dma-buf/Kconfig
index b46eb8a552d7..fdd823e446cc 100644
--- a/drivers/dma-buf/Kconfig
+++ b/drivers/dma-buf/Kconfig
@@ -55,7 +55,7 @@ config DMABUF_MOVE_NOTIFY
config DMABUF_DEBUG
bool "DMA-BUF debug checks"
depends on DMA_SHARED_BUFFER
- default y if DMA_API_DEBUG
+ default y if DEBUG
help
This option enables additional checks for DMA-BUF importers and
exporters. Specifically it validates that importers do not peek at the
--
2.43.0
next prev parent reply other threads:[~2025-12-05 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 13:06 [PATCH 1/2] dma-buf: improve sg_table debugging hack v3 Christian König
2025-12-05 13:06 ` Christian König [this message]
2025-12-05 16:02 ` [PATCH 2/2] dma-buf: enable DMABUF_DEBUG by default on DEBUG kernels Ruhl, Michael J
2025-12-05 16:01 ` [PATCH 1/2] dma-buf: improve sg_table debugging hack v3 Ruhl, Michael J
2025-12-05 18:25 ` Ruhl, Michael J
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 14:59 [PATCH 1/2] dma-buf: improve sg_table debugging hack v2 Christian König
2025-12-04 14:59 ` [PATCH 2/2] dma-buf: enable DMABUF_DEBUG by default on DEBUG kernels Christian König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251205130604.1582-2-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=matthew.auld@intel.com \
--cc=michael.j.ruhl@intel.com \
--cc=simona.vetter@ffwll.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox