platform: Clarify behavior for ATOMIC_SCOPE_ALL_DEVICES

KhronosGroup · Sep 9, 2024 · 695f7f2 · 695f7f2
1 parent 0134139
commit 695f7f2
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/api/opencl_platform_layer.asciidoc b/api/opencl_platform_layer.asciidoc
@@ -1606,6 +1606,9 @@ include::{generated}/api/version-notes/CL_DEVICE_ATOMIC_MEMORY_CAPABILITIES.asci
         {CL_DEVICE_ATOMIC_ORDER_RELAXED} \| +
         {CL_DEVICE_ATOMIC_SCOPE_WORK_GROUP}
 
+        A device that does not support CL_DEVICE_SVM_ATOMICS (and hence does not support CL_MEM_SVM_ATOMICS) may still support CL_DEVICE_ATOMIC_SCOPE_ALL_DEVICES. On these devices, an atomic operation with
+        memory_scope_all_svm_devices will behave the same as if the scope were memory_scope_device - refer to <<memory-consistency-model, memory consistency model>>
+
 | {CL_DEVICE_ATOMIC_FENCE_CAPABILITIES_anchor}
 
 include::{generated}/api/version-notes/CL_DEVICE_ATOMIC_FENCE_CAPABILITIES.asciidoc[]