1menu "DMABUF options" 2 3config SYNC_FILE 4 bool "Explicit Synchronization Framework" 5 default n 6 select ANON_INODES 7 select DMA_SHARED_BUFFER 8 ---help--- 9 The Sync File Framework adds explicit syncronization 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/sync_file.txt. 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 42endmenu 43