From 695f7f21ccb38ccdace1ff9c65167aa97e8b0f67 Mon Sep 17 00:00:00 2001 From: Sreelakshmi Haridas Maruthur Date: Mon, 9 Sep 2024 14:27:58 -0600 Subject: [PATCH 1/3] platform: Clarify behavior for ATOMIC_SCOPE_ALL_DEVICES --- api/opencl_platform_layer.asciidoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/api/opencl_platform_layer.asciidoc b/api/opencl_platform_layer.asciidoc index 2b1ae266d..9aece059e 100644 --- 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 <> + | {CL_DEVICE_ATOMIC_FENCE_CAPABILITIES_anchor} include::{generated}/api/version-notes/CL_DEVICE_ATOMIC_FENCE_CAPABILITIES.asciidoc[] From eb753c02c047dd1192c568f0c96111ab5b7f9338 Mon Sep 17 00:00:00 2001 From: Sreelakshmi Haridas Maruthur Date: Mon, 9 Sep 2024 15:53:04 -0600 Subject: [PATCH 2/3] Adjusted table widths to prevent overflow beyond a page Asciidr has a limitation that prevents table cells from spanning across pages --- api/opencl_platform_layer.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/api/opencl_platform_layer.asciidoc b/api/opencl_platform_layer.asciidoc index 9aece059e..b762e24d8 100644 --- a/api/opencl_platform_layer.asciidoc +++ b/api/opencl_platform_layer.asciidoc @@ -473,7 +473,7 @@ device except for the following queries: [[device-queries-table]] .List of supported param_names by {clGetDeviceInfo} -[width="100%",cols="<33%,<17%,<50%",options="header"] +[width="100%",cols="<28%,<15%,<57%",options="header"] |==== | Device Info | Return Type | Description | {CL_DEVICE_TYPE_anchor} From f26c90fca89ca366497a78d281f293e3f4f46433 Mon Sep 17 00:00:00 2001 From: Sreelakshmi Haridas Maruthur Date: Tue, 10 Sep 2024 11:53:17 -0600 Subject: [PATCH 3/3] Update api/opencl_platform_layer.asciidoc Co-authored-by: Ben Ashbaugh --- api/opencl_platform_layer.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/api/opencl_platform_layer.asciidoc b/api/opencl_platform_layer.asciidoc index b762e24d8..81f08b585 100644 --- a/api/opencl_platform_layer.asciidoc +++ b/api/opencl_platform_layer.asciidoc @@ -1606,8 +1606,8 @@ 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 <> + 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 the <>. | {CL_DEVICE_ATOMIC_FENCE_CAPABILITIES_anchor}