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
