feaure: Update docs to show DDI Driver Handles are default as of 1.17 (#473)

Signed-off-by: Neil R. Spruit <neil.r.spruit@intel.com>

Author: nrspruit

scripts/core/EXT_Driver_DDIHandles.rst

@@ -47,6 +47,26 @@ Handle Structures:
             zer_dditable_driver_t *pRuntime; // [in] pointer to _zer_dditable_t_ object related to this handle
         } ze_handle_t;
 
+Mandatory Support (Spec v1.17+):
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Starting from Level Zero spec version 1.17, support for this extension is **required** for any driver reporting API version 1.17 or later via ``${x}DriverGetApiVersion``.
+The loader does **not** need to query the extension property for such drivers — DDI handles are unconditionally available.
+
+.. note::
+
+    Drivers reporting API version 1.17 or later must support **extension version 1.1** of this extension, which corresponds to the full ``ze_handle_t`` structure including the ``pRuntime`` member (pointer to ``zer_dditable_driver_t``).
+    Such drivers **must** initialize ``pRuntime`` in every handle they allocate — at minimum with zeroed/empty function pointer values — so that the loader can safely dereference it without a null-pointer check.
+    A driver that sets ``pRuntime`` to ``nullptr`` while reporting API version 1.17 is non-conformant; any loader or application attempt to dispatch a ``zer_*`` call through that handle will result in undefined behavior (null pointer dereference / crash).
+
+For drivers reporting API version 1.16 or earlier, the loader must continue to check for this extension via ``${x}DriverGetExtensionProperties``
+before using DDI handles, preserving full backwards compatibility.
+
+This guarantee enables Level Zero extensions introduced in spec v1.17 or later to embed handles directly inside Level Zero structures
+(e.g., via ``pNext`` chains) without requiring the loader to translate or unwrap the handles.
+Additionally, drivers may assume the loader will dispatch calls exclusively via the DDI tables embedded in their handles;
+the only exception is the global DDI table used during driver initialization and to read the driver's reported API version.
+
 DDI Handles Extension:
 ~~~~~~~~~~~~~~~~~~~~~~
 

scripts/core/driver.yml

@@ -240,6 +240,7 @@ ordinal: "1"
 details:
     - "The application may call this function from simultaneous threads."
     - "The implementation of this function should be lock-free."
+    - "Starting from API version 1.17, any driver reporting version 1.17 or later is assumed to support the $X_DRIVER_DDI_HANDLES_EXT_NAME extension; see $x_driver_ddi_handles_ext_properties_t for details."
 params:
     - type: $x_driver_handle_t
       name: hDriver

scripts/core/driverDDIHandles.yml

@@ -49,3 +49,7 @@ members:
             [out] 0 (none) or a valid combination of ::ze_driver_ddi_handle_ext_flags_t
 details:
     - "This structure may be returned from $xDriverGetProperties, via the `pNext` member of $x_driver_properties_t."
+    - "Starting from spec version 1.17, support for this extension is assumed for any driver reporting API version 1.17 or later via $xDriverGetApiVersion; the loader does NOT need to query the extension property for such drivers."
+    - "For drivers reporting API version 1.16 or earlier, the loader must check for this extension before using DDI handles."
+    - "This guarantee enables Level Zero extensions introduced in spec v1.17 or later to embed handles directly inside Level Zero structures (e.g., via pNext chains) without requiring the loader to translate or unwrap handles."
+    - "Additionally, drivers may assume the loader will dispatch calls exclusively via the DDI tables embedded in their handles; the only exception is the global DDI table used during driver initialization and to read the reported API version."