CONFIG_SYNC_FILE: Explicit Synchronization Framework

General informations

The Linux kernel configuration item CONFIG_SYNC_FILE has multiple definitions:

Explicit Synchronization Framework found in drivers/dma-buf/Kconfig

The configuration item CONFIG_SYNC_FILE:

• prompt: Explicit Synchronization Framework
• type: bool
• depends on: (none)
• defined in drivers/dma-buf/Kconfig
• found in Linux kernels: 4.8–4.20, 5.0–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

The Sync File Framework adds explicit synchronization via userspace. It enables send/receive 'struct dma_fence' objects to/from userspace via Sync File fds for synchronization between drivers via userspace components. It has been ported from Android.

The first and main user for this is graphics in which a fence is associated with a buffer. When a job is submitted to the GPU a fence is attached to the buffer and is transferred via userspace, using Sync Files fds, to the DRM driver for example. More details at Documentation/driver-api/sync_file.rst.

sync_file support for fences found in drivers/dma-buf/Kconfig

The configuration item CONFIG_SYNC_FILE:

• prompt: sync_file support for fences
• type: bool
• depends on: (none)
• defined in drivers/dma-buf/Kconfig
• found in Linux kernels: 4.7

Help text

This option enables the fence framework synchronization to export sync_files to userspace that can represent one or more fences.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: