address comments

Signed-off-by: Sergey V Maslov <[email protected]>

Author: smaslov-intel

sycl/doc/extensions/LevelZeroBackend/LevelZeroBackend.md

@@ -101,7 +101,8 @@ backend_input_t<backend::ext_oneapi_level_zero,
 struct {
   ze_context_handle_t NativeHandle;
   std::vector<device> DeviceList;
-  ext::oneapi::level_zero::ownership Ownership;
+  ext::oneapi::level_zero::ownership Ownership{
+      ext::oneapi::level_zero::ownership::transfer};
 }
 ```
 </td>
@@ -113,7 +114,8 @@ struct {
 ``` C++
 struct {
   ze_command_queue_handle_t NativeHandle;
-  ext::oneapi::level_zero::ownership Ownership;
+  ext::oneapi::level_zero::ownership Ownership{
+      ext::oneapi::level_zero::ownership::transfer};
 }
 ```
 </td>
@@ -125,7 +127,8 @@ struct {
 ``` C++
 struct {
   ze_event_handle_t NativeHandle;
-  ext::oneapi::level_zero::ownership Ownership;
+  ext::oneapi::level_zero::ownership Ownership{
+      ext::oneapi::level_zero::ownership::transfer};
 }
 ```
 </td>
@@ -142,7 +145,8 @@ std::vector<ze_module_handle_t>
 ``` C++
 struct {
   ze_module_handle_t NativeHandle;
-  ext::oneapi::level_zero::ownership Ownership;
+  ext::oneapi::level_zero::ownership Ownership{
+      ext::oneapi::level_zero::ownership::transfer};
 }
 ```
 </td>
@@ -234,7 +238,20 @@ make_kernel_bundle<backend::ext_oneapi_level_zero,
     const context &Context)
 ```
 </td>
-<td>Constructs a SYCL kernel_bundle instance from a Level-Zero <code>ze_module_handle_t</code>. The <code>Context</code> argument must be a valid SYCL context encapsulating a Level-Zero context. The Level-Zero module should be created on the same context. The Level-Zero module must be fully linked (i.e. not require further linking through <a href="https://spec.oneapi.com/level-zero/latest/core/api.html?highlight=zemoduledynamiclink#_CPPv419zeModuleDynamicLink8uint32_tP18ze_module_handle_tP28ze_module_build_log_handle_t"><code>zeModuleDynamicLink</code></a>), and thus the SYCL kernel_bundle is created in the "executable" state. The <code>Ownership</code> input structure member specifies if the SYCL runtime should take ownership of the passed native handle. The default behavior is to transfer the ownership to the SYCL runtime. See section 4.4 for details. If the behavior is "transfer" then runtime is going to destroy the input Level-Zero module, and hence the application must not to have any outstanding <code>ze_kernel_handle_t</code> handles to the underlying <code>ze_module_handle_t</code> by the time this interoperability <code>kernel_bundle</code> destructor is called.</td>
+<td>Constructs a SYCL kernel_bundle instance from a Level-Zero
+<code>ze_module_handle_t</code>. The <code>Context</code> argument must be a
+valid SYCL context encapsulating a Level-Zero context, and the Level-Zero
+module must be created on the same context. The Level-Zero module must be
+fully linked (i.e. not require further linking through <a href="https://spec.oneapi.com/level-zero/latest/core/api.html?highlight=zemoduledynamiclink#_CPPv419zeModuleDynamicLink8uint32_tP18ze_module_handle_tP28ze_module_build_log_handle_t">
+<code>zeModuleDynamicLink</code></a>), and thus the SYCL kernel_bundle is
+created in the "executable" state. The <code>Ownership</code> input structure
+member specifies if the SYCL runtime should take ownership of the passed
+native handle. The default behavior is to transfer the ownership to the SYCL
+runtime. See section 4.4 for details. If the behavior is "transfer" then the
+runtime is going to destroy the input Level-Zero module, and hence the
+application must not to have any outstanding <code>ze_kernel_handle_t</code>
+handles to the underlying <code>ze_module_handle_t</code> by the time this
+interoperability <code>kernel_bundle</code> destructor is called.</td>
 </tr>
 </table>