With this change, init for sysman Engine API would not be done during zeInit.
init and thereby Engine API handle creation would be done only
when user explicitly requests to enumerate handles
using zesDeviceEnumEngineGroups
Related-To: LOCI-3127
Signed-off-by: Kulkarni, Ashwin Kumar <ashwin.kumar.kulkarni@intel.com>
Before performing gpu device reset, first all level zero resources
and gpu device specific resources have to be cleaned up. Also as
after device reset, state of gpu device would be lost.
Hence after performing gpu device reset, level zero device have
to be reinitialized by querying gpu device again.
This change is aimed at reinitializing the level zero resources
after gpu device reset, so that user could continue using level zero
devices after device reset.
Related-To: LOCI-2627
Signed-off-by: Jitendra Sharma <jitendra.sharma@intel.com>
Fix warnings related to unused/uninitialized variables etc.
Change-Id: I2e75ede434442d7b99d6e28253e7811aac205323
Signed-off-by: Jitendra Sharma <jitendra.sharma@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
This change adds support to get engine active time and timestamp
from PMU interface.
Change-Id: I486dcce9fef3c7dc3f73fb8c7ea4c0bd020a6807
Signed-off-by: Jitendra Sharma <jitendra.sharma@intel.com>
Updated all the getHandle routines to use the following
algorithm:
n = min(*pCount, available)
if (*pCount == 0 || *pCount > available) {
*pCount = available;
}
if (pArrayn != nullptr) {
for(i = 0; i < n; i++) {
pArray[i] = handle[i];
}
}
Change-Id: I3b2a2170c2b52d1651bddae4f85f361fd86167a0
Signed-off-by: Bill Jordan <bill.jordan@intel.com>
This change does the following:
- Implement API zetSysmanProcessesGetState.
- Implement ULT to validate zetSysmanProcessesGetState's implementation
- Redesign ULTs for zetSysmanDeviceGetProperties to mock only OS specific
classes, and validate zetSysmanDeviceGetProperties's implementation end
to end.
- Some bug fixes in code that are caught by these new ULTs
Change-Id: I4a83789771d32978576ff62859628df2c0c795ad
Signed-off-by: Jitendra Sharma <jitendra.sharma@intel.com>
- by Mocking sysfs class and implementing OSSpecific(Linux)
Change-Id: I2eabf24e44e92b72e73bc323206776440b330b83
Signed-off-by: SaiKishore Konda <saikishore.konda@intel.com>
- Fixing the engine sysfs node path
- Using default engine as RCS (compute) engine for engine APIs
- Updating the ULT for the same
Change-Id: If11aea422ac7e73b7f5fd0bc30d0918915d73848
Signed-off-by: SaiKishore Konda <saikishore.konda@intel.com>
Warchulski, Jaroslaw