/linux-5.19.10/drivers/comedi/drivers/ni_routing/tools/ |
D | Makefile | 36 comedi_h.py: $(INC_UAPI)/linux/comedi.h 49 ni_values.py: convert_c_to_py 52 csv-files : ni_values.py comedi_h.py 53 ./convert_py_to_csv.py 55 csv-blank : comedi_h.py 56 ./make_blank_csv.py 59 c-files : comedi_h.py 60 ./convert_csv_to_c.py --route_values --device_routes 70 $(RM) -rf comedi_h.py ni_values.py convert_c_to_py all_cfiles.c *.pyc \
|
D | .gitignore | 2 comedi_h.py 4 ni_values.py
|
/linux-5.19.10/tools/testing/selftests/tc-testing/plugin-lib/ |
D | README-PLUGINS | 1 tdc.py will look for plugins in a directory plugins off the cwd. 5 tdc.py 8 __init__.py 9 10-rootPlugin.py -> ../plugin-lib/rootPlugin.py 10 20-valgrindPlugin.py -> ../plugin-lib/valgrindPlugin.py 11 30-nsPlugin.py -> ../plugin-lib/nsPlugin.py 14 tdc.py will find them and use them.
|
/linux-5.19.10/Documentation/bpf/ |
D | drgn.rst | 17 bpf_inspect.py 23 `bpf_inspect.py`_ is a tool intended to inspect BPF programs and maps. It can argument 27 The main use-case `bpf_inspect.py`_ covers is to show BPF programs of types 37 % sudo bpf_inspect.py prog argument 44 % sudo bpf_inspect.py map 51 % sudo bpf_inspect.py p | grep test_pkt_access 77 % sudo bpf_inspect.py 78 usage: bpf_inspect.py [-h] {prog,p,map,m} ... 104 diff --git a/tools/bpf_inspect.py b/tools/bpf_inspect.py argument 106 --- a/tools/bpf_inspect.py [all …]
|
/linux-5.19.10/scripts/gdb/linux/ |
D | Makefile | 5 symlinks := $(patsubst $(srctree)/$(src)/%,%,$(wildcard $(srctree)/$(src)/*.py)) 21 always-y += constants.py 22 $(obj)/constants.py: $(src)/constants.py.in FORCE
|
/linux-5.19.10/Documentation/dev-tools/kunit/ |
D | running_tips.rst | 7 Using ``kunit.py run`` ("kunit tool") 18 ( cd "$(git rev-parse --show-toplevel)" && ./tools/testing/kunit/kunit.py run $@ ) 22 Early versions of ``kunit.py`` (before 5.6) didn't work unless run from 28 ``kunit.py run`` accepts an optional glob argument to filter tests. The format 36 $ ./tools/testing/kunit/kunit.py run 'sysctl*' 43 $ ./tools/testing/kunit/kunit.py run 'sysctl*.*write*' 55 ``kunit.py run`` (along with ``build``, and ``config``) supports a 64 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig 71 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit 97 $ ./tools/testing/kunit/kunit.py run --kernel_args=param=42 --kernel_args=param2=false [all …]
|
D | kunit-tool.rst | 10 kunit_tool is a script (``tools/testing/kunit/kunit.py``) that aids in building 43 ./tools/testing/kunit/kunit.py run 49 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all` 63 ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4/.kunitconfig 69 ./tools/testing/kunit/kunit.py run --help 82 ./tools/testing/kunit/kunit.py config 89 ./tools/testing/kunit/kunit.py build 96 ./tools/testing/kunit/kunit.py exec 115 ./tools/testing/kunit/kunit.py run --raw_output 122 ./tools/testing/kunit/kunit.py run --raw_output=kunit [all …]
|
D | faq.rst | 34 (``tools/testing/kunit/kunit.py``) that does not support other architectures. 70 1. Run ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output`` 73 2. Instead of running ``kunit.py run``, try running ``kunit.py config``, 74 ``kunit.py build``, and ``kunit.py exec`` independently. This can help track 76 can run it manually against ``stdin`` or a file with ``kunit.py parse``.) 79 after building the UML kernel (for example, by using ``kunit.py build``). 86 around, so you can see what config was used after running ``kunit.py run``. 90 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This 98 can be parsed with ``kunit.py parse``. For more details, see "KUnit on
|
D | run_wrapper.rst | 19 ./tools/testing/kunit/kunit.py run 33 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all 53 ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4/.kunitconfig 59 ./tools/testing/kunit/kunit.py run --help 111 ./tools/testing/kunit/kunit.py config 118 ./tools/testing/kunit/kunit.py build 126 ./tools/testing/kunit/kunit.py exec 141 ./tools/testing/kunit/kunit.py run --raw_output 151 ./tools/testing/kunit/kunit.py parse /var/log/dmesg 153 dmesg | ./tools/testing/kunit/kunit.py parse [all …]
|
D | start.rst | 20 ./tools/testing/kunit/kunit.py run 50 tools/testing/kunit/kunit.py config 54 ``.kunitconfig`` lives in the ``--build_dir`` used by kunit.py, which is 72 If you change the ``.kunitconfig``, kunit.py will trigger a rebuild of the 75 ``.kunitconfig``, kunit.py won't overwrite your changes. 84 ./tools/testing/kunit/kunit.py run 231 ./tools/testing/kunit/kunit.py run
|
D | architecture.rst | 161 kunit_tool is a Python script ``(tools/testing/kunit/kunit.py)`` 170 (For example: ``tools/testing/kunit/qemu_configs/powerpc.py``). 177 ``kunit_config.py`` includes the parsing Kconfigs code. The code which 178 runs ``make olddefconfig`` is a part of ``kunit_kernel.py``. You can 179 invoke this command via: ``./tools/testing/kunit/kunit.py config`` and 185 ``build`` argument: ``./tools/testing/kunit/kunit.py build``. 192 argument: ``./tools/testing/kunit/kunit.py exec``.
|
/linux-5.19.10/scripts/ |
D | spdxcheck-test.sh | 5 python3 scripts/spdxcheck.py $FILE 6 python3 scripts/spdxcheck.py - < $FILE 10 python3 scripts/spdxcheck.py > /dev/null
|
/linux-5.19.10/tools/testing/selftests/tc-testing/ |
D | README | 26 ./tdc.py -c 40 in the tdc_config.py file. Find the 'TC' entry in the NAMES dictionary and 45 ./tdc.py -p /path/to/tc 56 Tests that use a network device should have nsPlugin.py listed as a 65 ./tdc.py -h 103 The tdc_config.py file contains multiple values that can be altered to suit 117 Run tdc.py -h to see the full list of available arguments. 119 usage: tdc.py [-h] [-p PATH] [-D DIR [DIR ...]] [-f FILE [FILE ...]] 176 was in the tdc.py script has been moved into the plugins. 187 lrwxrwxrwx 1 bjb bjb 27 Oct 4 16:12 10-rootPlugin.py -> ../plugin-lib/rootPlugin.py [all …]
|
D | tdc.sh | 5 ./tdc.py -c actions --nobuildebpf 6 ./tdc.py -c qdisc
|
D | Makefile | 32 TEST_FILES := tdc*.py Tdc*.py plugins plugin-lib tc-tests
|
/linux-5.19.10/tools/perf/Documentation/ |
D | build-xed.txt | 7 $ ./mfile.py --share 8 $ ./mfile.py examples 9 $ sudo ./mfile.py --prefix=/usr/local install
|
D | db-export.txt | 10 tools/perf/scripts/python/export-to-sqlite.py 11 tools/perf/scripts/python/export-to-postgresql.py 29 3. Scripts that use a database (e.g. exported-sql-viewer.py) can maintain 31 before using them. e.g. function IsSelectable() in exported-sql-viewer.py
|
/linux-5.19.10/tools/testing/selftests/tpm2/ |
D | Makefile | 5 TEST_PROGS_EXTENDED := tpm2.py tpm2_tests.py
|
/linux-5.19.10/tools/power/pm-graph/ |
D | Makefile | 10 install sleepgraph.py $(DESTDIR)$(PREFIX)/lib/pm-graph 11 install bootgraph.py $(DESTDIR)$(PREFIX)/lib/pm-graph 26 ln -s ../lib/pm-graph/bootgraph.py $(DESTDIR)$(PREFIX)/bin/bootgraph 27 ln -s ../lib/pm-graph/sleepgraph.py $(DESTDIR)$(PREFIX)/bin/sleepgraph
|
D | README | 64 - python-requests (for stresstester.py) 128 %> sudo ./sleepgraph.py -modes 133 %> sudo ./sleepgraph.py -m mem -rtcwake 15 137 %> sudo ./sleepgraph.py -config config/suspend.cfg 169 %> sudo ./sleepgraph.py -m mem -rtcwake 15 -mindev 1 -dev 173 %> sudo ./sleepgraph.py -config config/suspend-dev.cfg 193 %> sudo ./sleepgraph.py -m mem -rtcwake 15 -x2 -x2delay 1000 -predelay 1000 -postdelay 1000 -proc 197 %> sudo ./sleepgraph.py -config config/suspend-proc.cfg 277 %> sudo ./sleepgraph.py -m mem -rtcwake 10 -dev -gzip -multi 2000 0 281 %> sudo ./sleepgraph.py -m mem -rtcwake 10 -dev -gzip -multi 2000 0 -skiphtml [all …]
|
/linux-5.19.10/scripts/kconfig/tests/ |
D | pytest.ini | 6 # the directory name that contains it. Use __init__.py for all test files. 7 python_files = __init__.py
|
/linux-5.19.10/Documentation/trace/ |
D | events-msr.rst | 35 The trace data can be post processed with the postprocess/decode_msr.py script:: 37 cat /sys/kernel/debug/tracing/trace | decode_msr.py /usr/src/linux/include/asm/msr-index.h
|
/linux-5.19.10/tools/perf/scripts/python/bin/ |
D | event_analyzing_sample-report | 3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/event_analyzing_sample.py
|
D | flamegraph-report | 3 perf script -s "$PERF_EXEC_PATH"/scripts/python/flamegraph.py -- "$@"
|
D | net_dropmonitor-report | 4 perf script -s "$PERF_EXEC_PATH"/scripts/python/net_dropmonitor.py $@
|