You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -50,3 +56,63 @@ The value of the variable is a bit-mask, with the following supported values:
50
56
- Enables tracing of PI calls
51
57
* - ``-1``
52
58
- Enables all levels of tracing
59
+
60
+
.. _env_var_ze_flat_device_hierarchy:
61
+
62
+
Variable ``ZE_FLAT_DEVICE_HIERARCHY``
63
+
--------------------------
64
+
Allows users to define the device hierarchy model exposed by Level Zero driver implementation.
65
+
Keep in mind :py:mod:`dpctl.get_composite_devices` will only work while this is set to ``COMBINED``.
66
+
67
+
.. list-table::
68
+
:header-rows: 1
69
+
70
+
* - Value
71
+
- Description
72
+
* - ``COMBINED``
73
+
- Level Zero devices with multiple tiles will be exposed as a set of root devices, each corresponding to an individual tile. These root devices are component devices, which can be queried for their corresponding composite device, and the composite device can in turn be queried for components. Dedicated composite device APIs will return non-trivial results.
74
+
* - ``COMPOSITE``
75
+
- Level Zero devices with multiple tiles will be exposed as a singular root device, with tiles accessible as sub-devices.
76
+
* - ``FLAT``
77
+
- Level Zero devices with multiple tiles will be exposed as a set of root devices, each corresponding to an individual tile. Enabled by default.
78
+
79
+
Read more about device hierarchy in `Level Zero Specification <https://oneapi-src.github.io/level-zero-spec/level-zero/latest/core/PROG.html#device-hierarchy>`_ and `Intel GPU article <https://www.intel.com/content/www/us/en/developer/articles/technical/flattening-gpu-tile-hierarchy.html>`_.
80
+
81
+
Variable ``ZE_AFFINITY_MASK``
82
+
-------------------------------
83
+
Allows users to mask specific devices from being used by SYCL applications.
84
+
If we have ``ZE_FLAT_DEVICE_HIERARCHY`` set to ``COMPOSITE``, we can have an AFFINITY of “1” for our application to only see device #1 - making system devices 0, and 2+, invisible.
85
+
86
+
If we have ``ZE_FLAT_DEVICE_HIERARCHY`` set to ``FLAT``, we can have a ``ZE_AFFINITY_MASK`` of “1” for our application to only see the second tile in the system as logical device #0.
87
+
If the system has four dual-tile GPUs installed, this would be the second tile in the first GPU. In ``FLAT`` mode, the numbers use a system-wide-sub-device-number from a flat numbering perspective.
88
+
Therefore, we could use the second tile in each of four dual-tile GPUs with ``ZE_AFFINITY_MASK=1,3,5,7``.
89
+
90
+
Additional examples to illustrate this are in the detailed documentation for ``ZE_AFFINITY_MASK``, read more about it in `Level Zero Specification <https://oneapi-src.github.io/level-zero-spec/level-zero/latest/core/PROG.html#affinity-mask>`_.
91
+
92
+
Variable ``ZE_ENABLE_PCI_ID_DEVICE_ORDER``
93
+
-------------------------------
94
+
Forces driver to report devices from lowest to highest PCI bus ID.
0 commit comments