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>
