store reference to std of root device indices and device bitfields
store NEO::Device in USM properties
Related-To: NEO-3691
Signed-off-by: Mateusz Jablonski <mateusz.jablonski@intel.com>
Shared-allocations are currently migrated to GPU by the page-fault
manager when calling executeCommandLists. Allocations to migrate are
taken from the lists container. However, if a shared-allocation
has been made resident with zeContextMakeMemoryResident(), it is not
added to the list container, and hence it is not migrated to device.
So, add a container of resident allocations to the driver and migrate
them along with the other allocations.
Signed-off-by: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
Add experimental extension to set global work offest in L0.
Current L0 specification does not have interface to export
experimental function symbols, so for now, applications need
to find the symbol like with dlsym on Linux.
A blackbox test showing functionality is also added.
Signed-off-by: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
Add ZE_experimental_module_program extension to L0 driver to support
multiple input modules being passed to zeModuleCreate().
Signed-off-by: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
Add support for passing ze_external_memory_import_fd_t extended
structure to zeMemAllocDevice() to allocate a device memory
out of an fd handle.
Signed-off-by: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
Add support for passing ze_external_memory_export_fd_t extended
structure to zeMemGetAllocProperties() to retrieve an fd handle
for a device allocation.
Signed-off-by: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
This patch does the following:
- Fixes a bug in FsAccess::listDirectory that could return
ZE_RESULT_UNKNOWN_ERROR when no error has occurred.
- Fixes a bug in zesDeviceReset that would reset the device
if force was set to false, even if the device was in use.
- Fixes a bug in zesDeviceReset that would reset the device
if force was set to false without closing the file descriptor.
- Added a releaseResources method method to Device object.
This method does the same thing as the DeviceImp
destructor except it does not free the DeviceImp object
and it does not free the SysmanDeviceImp object.
- Added the releaseResources methods to Mock<Device> object.
- Moved the reset of the debugger out of DriverHandleImp
destructor and into DeviceImp releaseResources.
- Added a releaseEngine method to the EngineHandleContext. This
method frees all the Engine handles.
- On reset, I call the Devcie->releaseResources and
EngineHandleContext->releaseEngines before resetting the device.
- Added a -r (--reset) option to zello_sysman so I
could easily test resets.
With these patches, the L0 Sysman CTS for zesDeviceReset
both pass.
Change-Id: I31fad1b27bc5cc6befe31cd6f9319748e2683424
- Changed Global Driver to be a void * to avoid auto add of Global
Driver Destructor to run before destruction of other L0 data structures
that might be enqueued to destory in static object destructors.
- Added register of library unload driverdestructor to cleanup
driver/device as the last destructor run.
Change-Id: I8ba6c5c27424b942a86a2613edd52fc682ab1c64
Signed-off-by: Spruit, Neil R <neil.r.spruit@intel.com>
Read the env var in hexadecimal format, as spec defines it,
and allow for empty string to be the same as default value.
Change-Id: I201c81733ac3d55a5c9ba50b42e28a8cf3414a6d
Signed-off: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
So initialization fails gracefully when Level Zero is
executed in unsupported platforms.
Change-Id: I06bd9f00260ebb1266108bd4ccee7abbc9275200
Signed-off: Jaime Arteaga <jaime.a.arteaga.molina@intel.com>
We use the first device associated with the driver when no device
is explicitly provided.
Event pools are no longer created via a device method.
Change-Id: Ib16dc79be3ceb1f822c7c1dace7264a0052a6593
Signed-off-by: Jim Snow <jim.m.snow@intel.com>
Lukasz Jobczyk