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

docs/user_guide: Clarify basic run command information.

Browse Source
This commit is contained in:
Marc Bonnici
2018-04-25 15:11:58 +01:00
committed by setrofim
parent 81c6da9c2c
commit 8c9c1a8f1e
1 changed files with 12 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
doc/source/user_guide.rst
View File

@@ -408,16 +408,21 @@ redirect the output to a different directory we can use::
wa run dhrystone -d my_output_directory wa run dhrystone -d my_output_directory
We can also tell WA to use a different config.yaml file by supplying with with the ``-c`` argument. We can also tell WA to use additional config files by supplying it with
One use case for passing additional config files is if you have multiple devices the ``-c`` argument. One use case for passing additional config files is if you
you wish test with WA, you can store the relevant device configuration in have multiple devices you wish test with WA, you can store the relevant device
individual config files and then pass the file corresponding to the device you wish configuration in individual config files and then pass the file corresponding to
to use for that particular test.:: the device you wish to use for that particular test.
wa run -c myconfig.yaml dhrystone .. note:: As previously mentioned, any more specific configuration present in
the agenda file will overwrite the corresponding config parameters
specified in the config file(s).
::
wa run -c myconfig.yaml ~/myagenda.yaml
To use the same output directory but override the existing contents to To use the same output directory but override the existing contents to
store new dhrystone resultswe:: store new dhrystone results we can specify the ``-f`` argument::
wa run -f dhrystone wa run -f dhrystone