| 98d1e54def96a88c70997f7882a384926297c043 |
|
02-Jun-2014 |
Alex Miller <milleral@chromium.org> |
Refactor service stopping into service_stopper in cleanup/initialize.
And there's some cleanup of hardware_TPMTakeOwnership snuck in here to
update the style a bit, and convert it into actually using the
service_stopper API.
TEST=None
BUG=None
Change-Id: I888cb00a6f17467e822793b6b6b0a7cca701a3cc
Reviewed-on: https://chromium-review.googlesource.com/202343
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Darren Krahn <dkrahn@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/client/site_tests/hardware_TPMTakeOwnership/hardware_TPMTakeOwnership.py
|
| 39b8432d6c8ef9d3efefce502e82b9ceae59a57a |
|
23-Sep-2011 |
Tan Gao <tgao@chromium.org> |
Develop an Autotest test case to measure TPM_TakeOwnership timing data
BUG=chrome-os-partner:6011
TEST=manual (special TTCI board required to conduct test)
Change details
- add new Autotest test case to measure timing delay of TPM_TakeOwnership operation
- define a new test suite that invokes hardware_TPMTakeOwnership test
(more tests may be added later)
- user may specify the number of iterations the test should run via
"loop" variable in suite control file
- user may specify the max acceptable delay in seconds via
"max_acceptable_delay_in_sec" variable in suite control file
- user can enforce upper limit of timing measurement via
"constraints=" clause in suite control file
Change-Id: I259e0e6ade74ed881d16c321637ced079e4958e1
Reviewed-on: http://gerrit.chromium.org/gerrit/8230
Reviewed-by: Ang Pan <oscarpan@chromium.org>
Tested-by: Tan Gao <tgao@chromium.org>
Commit-Ready: Tan Gao <tgao@chromium.org>
/external/autotest/client/site_tests/hardware_TPMTakeOwnership/hardware_TPMTakeOwnership.py
|