Home
last modified time | relevance | path

Searched refs:py (Results 1 – 25 of 84) sorted by relevance

1234

/Linux-v5.10/drivers/staging/comedi/drivers/ni_routing/tools/
DMakefile35 comedi_h.py : ../../../comedi.h
41 ni_values.py: convert_c_to_py
44 csv-files : ni_values.py comedi_h.py
45 ./convert_py_to_csv.py
48 ./make_blank_csv.py
51 c-files : comedi_h.py
52 ./convert_csv_to_c.py --route_values --device_routes
62 $(RM) -rf comedi_h.py ni_values.py convert_c_to_py all_cfiles.c *.pyc \
D.gitignore2 comedi_h.py
4 ni_values.py
/Linux-v5.10/tools/testing/selftests/tc-testing/plugin-lib/
DREADME-PLUGINS1 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-v5.10/Documentation/bpf/
Ddrgn.rst17 bpf_inspect.py
23 `bpf_inspect.py`_ is a tool intended to inspect BPF programs and maps. It can
27 The main use-case `bpf_inspect.py`_ covers is to show BPF programs of types
37 % sudo bpf_inspect.py prog
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
106 --- a/tools/bpf_inspect.py
[all …]
/Linux-v5.10/scripts/gdb/linux/
DMakefile5 symlinks := $(patsubst $(srctree)/$(src)/%,%,$(wildcard $(srctree)/$(src)/*.py))
21 extra-y += constants.py
22 $(obj)/constants.py: $(src)/constants.py.in FORCE
/Linux-v5.10/scripts/
Dspdxcheck-test.sh6 $PYTHON scripts/spdxcheck.py $FILE
7 $PYTHON scripts/spdxcheck.py - < $FILE
11 $PYTHON scripts/spdxcheck.py > /dev/null
/Linux-v5.10/tools/testing/selftests/tc-testing/
DREADME26 ./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 …]
Dtdc.sh4 ./tdc.py -c actions --nobuildebpf
5 ./tdc.py -c qdisc
DMakefile33 TEST_FILES := tdc*.py Tdc*.py plugins plugin-lib tc-tests
/Linux-v5.10/tools/perf/Documentation/
Dbuild-xed.txt7 $ ./mfile.py --share
8 $ ./mfile.py examples
9 $ sudo ./mfile.py --prefix=/usr/local install
Ddb-export.txt10 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-v5.10/Documentation/dev-tools/kunit/
Dfaq.rst34 like the KUnit Wrapper (``tools/testing/kunit/kunit.py``) that does not support
71 1. Try running ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
74 2. Instead of running ``kunit.py run``, try running ``kunit.py config``,
75 ``kunit.py build``, and ``kunit.py exec`` independently. This can help track
77 can run it manually against stdin or a file with ``kunit.py parse``.)
80 building the UML kernel (e.g., by using ``kunit.py build``). Note that UML
87 around, so you can see what config was used after running ``kunit.py run``.
91 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This
99 can be parsed with ``kunit.py parse``. For more details, see "KUnit on
Dkunit-tool.rst10 kunit_tool is a script (``tools/testing/kunit/kunit.py``) that aids in building
38 ./tools/testing/kunit/kunit.py run
44 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all`
57 ./tools/testing/kunit/kunit.py run --help
/Linux-v5.10/tools/testing/selftests/tpm2/
DMakefile5 TEST_PROGS_EXTENDED := tpm2.py tpm2_tests.py
/Linux-v5.10/tools/power/pm-graph/
DMakefile10 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
DREADME64 - python-requests (for googlesheet.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-v5.10/scripts/kconfig/tests/
Dpytest.ini6 # the directory name that contains it. Use __init__.py for all test files.
7 python_files = __init__.py
/Linux-v5.10/Documentation/trace/
Devents-msr.rst35 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-v5.10/tools/perf/scripts/python/bin/
Dcompaction-times-report4 perf script -s "$PERF_EXEC_PATH"/scripts/python/compaction-times.py $@
Devent_analyzing_sample-report3 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/event_analyzing_sample.py
Dflamegraph-report3 perf script -s "$PERF_EXEC_PATH"/scripts/python/flamegraph.py -- "$@"
Dnet_dropmonitor-report4 perf script -s "$PERF_EXEC_PATH"/scripts/python/net_dropmonitor.py $@
Dnetdev-times-report5 perf script -s "$PERF_EXEC_PATH"/scripts/python/netdev-times.py $@
Dstackcollapse-report3 perf script -s "$PERF_EXEC_PATH"/scripts/python/stackcollapse.py -- "$@"
Dfutex-contention-report4 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/futex-contention.py

1234