sascha/workload-automation
1
0
Fork 0
mirror of https://github.com/ARM-software/workload-automation.git synced 2025-05-14 05:15:21 +01:00
Code Issues Releases Wiki Activity

doc/migration_guide: Fix typo

Browse Source
This commit is contained in:
Marc Bonnici 2018-04-26 10:56:55 +01:00 committed by setrofim
parent 61a9c96a7d
commit 504703d444
3 changed files with 3 additions and 3 deletions
doc/source
how_tos/users
agenda.rst
migration_guide.rst
user_reference
runtime_parameters.rst

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

@ -144,7 +144,7 @@ In addition to configuring the workload itself, we can also specify
configuration for the underlying device which can be done by setting runtime configuration for the underlying device which can be done by setting runtime
parameters in the workload spec. Explict runtime paremeters have been exposed for parameters in the workload spec. Explict runtime paremeters have been exposed for
configuring cpufreq, hotplug and cpuidle. For more detailed information on Runtime configuring cpufreq, hotplug and cpuidle. For more detailed information on Runtime
Parameters see the :ref:`runtime parmeters <runtime-parmeters>` section. For Parameters see the :ref:`runtime parmeters <runtime-parameters>` section. For
example, suppose we want to ensure the maximum score for our benchmarks, at the example, suppose we want to ensure the maximum score for our benchmarks, at the
expense of power consumption so we want to set the cpufreq governor to expense of power consumption so we want to set the cpufreq governor to
"performance" and enable all of the cpus on the device, (assuming there are 8 "performance" and enable all of the cpus on the device, (assuming there are 8

2
doc/source/migration_guide.rst

@ -62,7 +62,7 @@ All augmentations can now been enabled and disabled on a per workload basis.
Setting Runtime Parameters Setting Runtime Parameters
^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^
:ref:`Runtime Parameters <runtime-parmeters>` are now the preferred way of :ref:`Runtime Parameters <runtime-parameters>` are now the preferred way of
configuring, cpufreq, hotplug and cpuidle rather setting the corresponding configuring, cpufreq, hotplug and cpuidle rather setting the corresponding
sysfile values as this will perform additional validation and ensure the nodes sysfile values as this will perform additional validation and ensure the nodes
are set in the correct order to avoid any conflicts. are set in the correct order to avoid any conflicts.

2
doc/source/user_reference/runtime_parameters.rst

@ -1,4 +1,4 @@
.. _runtime-parmeters: .. _runtime-parameters:
Runtime Parameters Runtime Parameters
------------------ ------------------