diff options
| author | Axel Davy <[email protected]> | 2016-12-19 19:51:13 +0100 |
|---|---|---|
| committer | Axel Davy <[email protected]> | 2016-12-20 23:44:20 +0100 |
| commit | 1736ef65701d915cb5c4c7e489d35da4df47b58e (patch) | |
| tree | fd458a70eea56d59d783aae232322721756269de /src/gallium/docs | |
| parent | fbb4af96c6b6be08ed93e8d5a704b9f7002642f8 (diff) | |
gallium-docs: Add documentation for threading requirements
Add documentation for the requirements related to threading
for screens and contexts.
Signed-off-by: Axel Davy <[email protected]>
Reviewed-by: Marek Olšák <[email protected]>
Diffstat (limited to 'src/gallium/docs')
| -rw-r--r-- | src/gallium/docs/source/screen.rst | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst index 7ac39ffc44f..86aa2591abe 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -737,3 +737,13 @@ query group at the specified **index** is returned in **info**. The function returns non-zero on success. The driver-specific query group is described with the pipe_driver_query_group_info structure. + + +Thread safety +------------- + +Screen methods are required to be thread safe. While gallium rendering +contexts are not required to be thread safe, it is required to be safe to use +different contexts created with the same screen in different threads without +locks. It is also required to be safe using screen methods in a thread, while +using one of its contexts in another (without locks). |