1# SPDX-License-Identifier: GPL-2.0-only 2menu "DMABUF options" 3 4config SYNC_FILE 5 bool "Explicit Synchronization Framework" 6 default n 7 select DMA_SHARED_BUFFER 8 help 9 The Sync File Framework adds explicit synchronization via 10 userspace. It enables send/receive 'struct dma_fence' objects to/from 11 userspace via Sync File fds for synchronization between drivers via 12 userspace components. It has been ported from Android. 13 14 The first and main user for this is graphics in which a fence is 15 associated with a buffer. When a job is submitted to the GPU a fence 16 is attached to the buffer and is transferred via userspace, using Sync 17 Files fds, to the DRM driver for example. More details at 18 Documentation/driver-api/sync_file.rst. 19 20config SW_SYNC 21 bool "Sync File Validation Framework" 22 default n 23 depends on SYNC_FILE 24 depends on DEBUG_FS 25 help 26 A sync object driver that uses a 32bit counter to coordinate 27 synchronization. Useful when there is no hardware primitive backing 28 the synchronization. 29 30 WARNING: improper use of this can result in deadlocking kernel 31 drivers from userspace. Intended for test and debug only. 32 33config UDMABUF 34 bool "userspace dmabuf misc driver" 35 default n 36 depends on DMA_SHARED_BUFFER 37 depends on MEMFD_CREATE || COMPILE_TEST 38 help 39 A driver to let userspace turn memfd regions into dma-bufs. 40 Qemu can use this to create host dmabufs for guest framebuffers. 41 42config DMABUF_MOVE_NOTIFY 43 bool "Move notify between drivers (EXPERIMENTAL)" 44 default n 45 help 46 Don't pin buffers if the dynamic DMA-buf interface is available on 47 both the exporter as well as the importer. This fixes a security 48 problem where userspace is able to pin unrestricted amounts of memory 49 through DMA-buf. 50 This is marked experimental because we don't yet have a consistent 51 execution context and memory management between drivers. 52 53config DMABUF_DEBUG 54 bool "DMA-BUF debug checks" 55 default y if DMA_API_DEBUG 56 help 57 This option enables additional checks for DMA-BUF importers and 58 exporters. Specifically it validates that importers do not peek at the 59 underlying struct page when they import a buffer. 60 61config DMABUF_SELFTESTS 62 tristate "Selftests for the dma-buf interfaces" 63 default n 64 depends on DMA_SHARED_BUFFER 65 66menuconfig DMABUF_HEAPS 67 bool "DMA-BUF Userland Memory Heaps" 68 select DMA_SHARED_BUFFER 69 help 70 Choose this option to enable the DMA-BUF userland memory heaps. 71 This options creates per heap chardevs in /dev/dma_heap/ which 72 allows userspace to allocate dma-bufs that can be shared 73 between drivers. 74 75source "drivers/dma-buf/heaps/Kconfig" 76 77endmenu 78