OpenCL coarse-grained SVM buffer sharing and regional time zone handling
0 reputation · 29 Jun 2021, 12:11 UTC
Goal: confirm whether OpenCL coarse-grained SVM requires host-side regional time zone conversion to complete before clEnqueueSVMMap, and whether the specification defines ordering between date preparation and buffer mapping.
OpenCL 2.0 coarse-grained SVM lets a host allocate one buffer with clSVMAlloc and share the same pointer with kernels. The host must relinquish access before kernel execution, typically using clEnqueueSVMMap and clEnqueueSVMUnmap with event dependencies. OpenCL provides no built-in regional time zone or date conversion API, so calendar logic must run on the host or in OpenCL C before the buffer is mapped for device use.
Uncertainty: the specification does not prescribe a required event ordering between host time zone conversion and clEnqueueSVMMap, nor does it define kernel argument serialization for localized date values. Overlapping host and device access to the same buffer region remains implementation-defined outside map/unmap boundaries.
Does OpenCL require host date conversion to finish before clEnqueueSVMMap? Is there a defined ordering between time zone preparation and SVM mapping events? How should localized date values be serialized as kernel arguments?