This patch adds two ULTs.
Verify that an IN USE error is returned if the device is open by another
process.
Verify that reset succeeds if device is not in use.
Verify that reset with force succeeds if device is in use.
Verify that reset without force succeeds if device is opened during
reset, and process is killed.
Verify that reset with force fails with device in use
if device is opened during reset, and process will not die
Change-Id: I232572c192bc481d8d63ef39c7494976100325ff
Signed-off-by: Bill Jordan <bill.jordan@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
In this Change:
- Initialize local variables used in pci source.
- Move setting of temperature handle's type to constructor of
TemperatureImp class as temperature handle's type is used in
init() of TemperatureImp class.
- Allow only ENOENT errno at the end of FsAccess::listDirectory function.
Because in this function all directory entries will be read in a
loop. And loop will exit only after readdir() finished reading
all entries in directory and thus readdir() will exit, when it fails
reading any further entry. Thus system will return ENOENT for readdir.
Change-Id: Ibd3ac3f841b114fd87edea1410750b33f3a14e5b
Signed-off-by: Jitendra Sharma <jitendra.sharma@intel.com>
- added dual handle support for RAS Correctable and Uncorrectable Errors.
- added reset counter for RAS.
- added Os Specific ULT for RAS
Change-Id: Ia10115bf6720ab211f549571e810ec0d6c0801ec
If after reading clients directory, while actually trying to
access the individual clients file, we receive a error
ZET_RESULT_ERROR_NOT_AVAILABLE, then it means that this process/client
might be killed/removed. Hence dont return error to user.
Instead simply skip that client's traversal further and move on
to next available client.
Change-Id: If86610a89d7b2421fd85560e5a223391b76d78a0
Signed-off-by: Jitendra Sharma <jitendra.sharma@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>
Implemented function level reset.
Implementation is:
Make sure we are root (otherwise, return insufficient permissions)
Make sure no one has the device open
(otherwise, return hande object in use)
Close our file handle
Unbind the device from the kernel driver
Make sure no one still has the device open
(otherwise, kill them)
Perform function level reset (FLR)
Rebind the device to the kernel driver
Change-Id: Ic57b95487e73b5a5f2d03e619d813bf4199adf40
Signed-off-by: Bill Jordan <bill.jordan@intel.com>
Bill Jordan