sascha/workload-automation
1
0
Fork 0
mirror of https://github.com/ARM-software/workload-automation.git synced 2025-04-18 00:30:47 +01:00
Code Issues Releases Wiki Activity

doc: Update RebootPolicy and ExectionOrder information

Browse Source
This commit is contained in:
Marc Bonnici 2018-05-22 17:54:48 +01:00 committed by setrofim
parent dc41af1f3f
commit cacc4dec8b
3 changed files with 11 additions and 4 deletions

2
doc/source/how_tos/users/agenda.rst

@ -180,7 +180,7 @@ execution, so all subsequent iterations will also be affected unless they
explicitly change the parameter (in the example above, performance governor will explicitly change the parameter (in the example above, performance governor will
also be used for ``memcpy`` and ``cyclictest``. There are two ways around this: also be used for ``memcpy`` and ``cyclictest``. There are two ways around this:
either set ``reboot_policy`` WA setting (see :ref:`configuration-specification` either set ``reboot_policy`` WA setting (see :ref:`configuration-specification`
section) such that the device gets rebooted between spec executions, thus being section) such that the device gets rebooted between job executions, thus being
returned to its initial state, or set the default runtime parameter values in returned to its initial state, or set the default runtime parameter values in
the ``config`` section of the agenda so that they get set for every spec that the ``config`` section of the agenda so that they get set for every spec that
doesn't explicitly override them. doesn't explicitly override them.

6
doc/source/how_tos/users/device_setup.rst

@ -293,9 +293,9 @@ Reboot Policy
^^^^^^^^^^^^^ ^^^^^^^^^^^^^
This indicates when during WA execution the device will be rebooted. By default This indicates when during WA execution the device will be rebooted. By default
this is set to ``as_needed``, indicating that WA will not reboot the device. Please this is set to ``as_needed``, indicating that WA will only reboot the device if
see ``reboot_policy`` documentation in :ref:`configuration-specification` for it becomes unresponsive. Please see ``reboot_policy`` documentation in
more details. :ref:`configuration-specification` for more details.
Execution Order Execution Order
^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^

7
doc/source/migration_guide.rst

@ -81,6 +81,13 @@ the new parameter names should be preferred:
whether a package on the target or the host should have priority when whether a package on the target or the host should have priority when
searching for a suitable package. searching for a suitable package.
- The execution order ``by_spec`` is now called ``by_workload`` for clarity of
purpose. For more information please see :ref:`configuration-specification`.
- The ``by_spec`` reboot policy has been removed as this is no longer relevant
and the ``each_iteration`` reboot policy has been renamed to ``each_job``,
please see :ref:`configuration-specification` for more information.
Individual workload parameters have been attempted to be standardized for the Individual workload parameters have been attempted to be standardized for the
more common operations e.g.: more common operations e.g.: