resolve issue about devices and sub-devices

Author: bashbaug

extensions/cl_khr_unified_svm.asciidoc

@@ -1112,10 +1112,10 @@ For reference, for other APIs:
 . What about devices and sub-devices?
 +
 --
-*UNRESOLVED*: Neither the OpenCL specification nor this extension specification currently says much about how SVM behaves for devices and sub-devices.
+`RESOLVED`:
+In this extension, there is no implicit requirement that an allocation owned by a sub-device is accessible to its parent device or that an allocation owned by a parent device is accessible to its sub-device.
 
-My rough expectations are that if an allocation is made against a context with a device and a sub-device, and the allocation is associated with the device, then the allocation is also accessible to the sub-device.
-Unless additional clarification is needed, perhaps this issue may simply be resolved.
+The query for {clGetSVMPointerInfoKHR}({CL_SVM_ALLOC_ACCESS_FLAGS_KHR}) can be used to determine whether an allocation is accessible to a parent device or a sub-device, just like for any other device.
 --
 
 . Should we move more of the {clSVMAllocWithPropertiesKHR} arguments to properties?