diff options
| author | Andy Shevchenko <andriy.shevchenko@linux.intel.com> | 2013-07-23 18:36:46 +0300 |
|---|---|---|
| committer | Dan Williams <djbw@fb.com> | 2013-08-22 22:57:32 -0700 |
| commit | a6c268d033b1f363e0d76c0483a0f99266542820 (patch) | |
| tree | aa8c3a5c286637c15ebe18ebe4d65d593d5bd783 /Documentation/dmatest.txt | |
| parent | c095ba7224d8edc71dcef0d655911399a8bd4a3f (diff) | |
| download | op-kernel-dev-a6c268d033b1f363e0d76c0483a0f99266542820.zip op-kernel-dev-a6c268d033b1f363e0d76c0483a0f99266542820.tar.gz | |
dmatest: make module parameters writable
The debugfs interface brought a copy of the test case parameters. This makes
different set of values under /sys/module/dmatest/parameters/ and
/sys/kernel/debug/dmatest/. The user might be confused by the divergence of
values.
The proposed solution in this patch is to make module parameters writable and
remove them from the debugfs. Though we're still using debugfs to control test
runner and getting results.
Documentation part is updated accordingly.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Suggested-by: Dan Williams <djbw@fb.com>
Signed-off-by: Dan Williams <djbw@fb.com>
Diffstat (limited to 'Documentation/dmatest.txt')
| -rw-r--r-- | Documentation/dmatest.txt | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/Documentation/dmatest.txt b/Documentation/dmatest.txt index 132a094..a2b5663 100644 --- a/Documentation/dmatest.txt +++ b/Documentation/dmatest.txt @@ -16,15 +16,16 @@ be built as module or inside kernel. Let's consider those cases. Part 2 - When dmatest is built as a module... After mounting debugfs and loading the module, the /sys/kernel/debug/dmatest -folder with nodes will be created. They are the same as module parameters with -addition of the 'run' node that controls run and stop phases of the test. +folder with nodes will be created. There are two important files located. First +is the 'run' node that controls run and stop phases of the test, and the second +one, 'results', is used to get the test case results. Note that in this case test will not run on load automatically. Example of usage: - % echo dma0chan0 > /sys/kernel/debug/dmatest/channel - % echo 2000 > /sys/kernel/debug/dmatest/timeout - % echo 1 > /sys/kernel/debug/dmatest/iterations + % echo dma0chan0 > /sys/module/dmatest/parameters/channel + % echo 2000 > /sys/module/dmatest/parameters/timeout + % echo 1 > /sys/module/dmatest/parameters/iterations % echo 1 > /sys/kernel/debug/dmatest/run Hint: available channel list could be extracted by running the following @@ -55,8 +56,8 @@ for the first performed test. After user gets a control, the test could be re-run with the same or different parameters. For the details see the above section "Part 2 - When dmatest is built as a module..." -In both cases the module parameters are used as initial values for the test case. -You always could check them at run-time by running +In both cases the module parameters are used as the actual values for the test +case. You always could check them at run-time by running % grep -H . /sys/module/dmatest/parameters/* Part 4 - Gathering the test results |
