/linux-6.3-rc2/drivers/comedi/drivers/ni_routing/tools/ |
A 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 \
|
A D | .gitignore | 2 comedi_h.py 4 ni_values.py
|
/linux-6.3-rc2/tools/testing/selftests/tc-testing/plugin-lib/ |
A 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-6.3-rc2/tools/verification/dot2/ |
A D | Makefile | 19 $(INSTALL) automata.py -D -m 644 $(DESTDIR)$(PYLIB)/dot2/automata.py 20 $(INSTALL) dot2c.py -D -m 644 $(DESTDIR)$(PYLIB)/dot2/dot2c.py 22 $(INSTALL) dot2k.py -D -m 644 $(DESTDIR)$(PYLIB)/dot2/dot2k.py
|
/linux-6.3-rc2/Documentation/bpf/ |
A D | drgn.rst | 17 bpf_inspect.py 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 107 +++ b/tools/bpf_inspect.py 122 % sudo bpf_inspect.py p [all …]
|
/linux-6.3-rc2/scripts/gdb/linux/ |
A 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-6.3-rc2/Documentation/dev-tools/kunit/ |
A D | running_tips.rst | 7 Using ``kunit.py run`` ("kunit tool") 22 Early versions of ``kunit.py`` (before 5.6) didn't work unless run from 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 139 $ ./tools/testing/kunit/kunit.py run --make_options=CC=/usr/bin/gcc-6 203 failed (as of 5.13). But ``kunit.py parse`` would, see below. 217 results in the same familiar format that ``kunit.py run`` does. [all …]
|
A D | faq.rst | 34 (``tools/testing/kunit/kunit.py``) that might not support some architectures 73 1. Run ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output`` 76 2. Instead of running ``kunit.py run``, try running ``kunit.py config``, 77 ``kunit.py build``, and ``kunit.py exec`` independently. This can help track 79 can run it manually against ``stdin`` or a file with ``kunit.py parse``.) 82 after building the UML kernel (for example, by using ``kunit.py build``). 89 around, so you can see what config was used after running ``kunit.py run``. 93 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This 101 can be parsed with ``kunit.py parse``. For more details, see :ref:`kunit-on-qemu`.
|
A D | start.rst | 24 ./tools/testing/kunit/kunit.py run 30 This happens because internally kunit.py specifies ``.kunit`` 77 tools/testing/kunit/kunit.py config 99 ./tools/testing/kunit/kunit.py run \ 105 ./tools/testing/kunit/kunit.py run \ 112 ``.kunitconfig``, kunit.py won't overwrite your changes. 135 ./tools/testing/kunit/kunit.py run "kunit_executor_test" 140 ./tools/testing/kunit/kunit.py run "example.example_simple_test" 146 ./tools/testing/kunit/kunit.py run "*.*64*" 279 ./tools/testing/kunit/kunit.py run [all …]
|
A D | run_wrapper.rst | 19 ./tools/testing/kunit/kunit.py run 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 153 dmesg | ./tools/testing/kunit/kunit.py parse 201 ./tools/testing/kunit/kunit.py run --arch=x86_64 208 ./tools/testing/kunit/kunit.py run \ 219 ``tools/testing/kunit/qemu_configs/x86_64.py``. [all …]
|
A D | architecture.rst | 159 ``kunit_tool`` is a Python script, found in ``tools/testing/kunit/kunit.py``. It 170 (for example, ``tools/testing/kunit/qemu configs/powerpc.py``) contains 177 file ``.kunitconfig``. The ``kunit_config.py`` script contains the code for parsing 179 ``kunit_kernel.py`` script. You can invoke this command through: 180 ``./tools/testing/kunit/kunit.py config`` and 186 ``build`` argument: ``./tools/testing/kunit/kunit.py build``. 193 argument: ``./tools/testing/kunit/kunit.py exec``.
|
/linux-6.3-rc2/scripts/ |
A D | spdxcheck-test.sh | 5 python3 scripts/spdxcheck.py $FILE 6 python3 scripts/spdxcheck.py - < $FILE 10 python3 scripts/spdxcheck.py > /dev/null
|
/linux-6.3-rc2/tools/testing/selftests/tc-testing/ |
A D | README | 26 ./tdc.py -c 45 ./tdc.py -p /path/to/tc 65 ./tdc.py -h 187 lrwxrwxrwx 1 bjb bjb 27 Oct 4 16:12 10-rootPlugin.py -> ../plugin-lib/rootPlugin.py 188 lrwxrwxrwx 1 bjb bjb 25 Oct 12 17:55 20-nsPlugin.py -> ../plugin-lib/nsPlugin.py 189 -rwxr-xr-x 1 bjb bjb 0 Sep 29 15:56 __init__.py 224 TdcPlugin.py. To use the plugin, you have to put the 230 - rootPlugin.py: 232 - nsPlugin.py: 235 - valgrindPlugin.py [all …]
|
A D | tdc.sh | 5 ./tdc.py -c actions --nobuildebpf 6 ./tdc.py -c qdisc
|
A D | Makefile | 31 TEST_FILES := tdc*.py Tdc*.py plugins plugin-lib tc-tests
|
/linux-6.3-rc2/tools/perf/Documentation/ |
A D | build-xed.txt | 7 $ ./mfile.py --share 8 $ ./mfile.py examples 9 $ sudo ./mfile.py --prefix=/usr/local install
|
A 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-6.3-rc2/tools/testing/selftests/tpm2/ |
A D | Makefile | 5 TEST_PROGS_EXTENDED := tpm2.py tpm2_tests.py
|
/linux-6.3-rc2/tools/perf/pmu-events/ |
A D | Build | 8 JEVENTS_PY = pmu-events/jevents.py 9 METRIC_PY = pmu-events/metric.py 10 METRIC_TEST_PY = pmu-events/metric_test.py
|
A D | metric.py | 531 py = orig.strip() 532 py = re.sub(r'([a-zA-Z][^-+/\* \\\(\),]*(?:\\.[^-+/\* \\\(\),]*)*)', 533 r'Event(r"\1")', py) 534 py = re.sub(r'#Event\(r"([^"]*)"\)', r'Literal("#\1")', py) 535 py = re.sub(r'([0-9]+)Event\(r"(e[0-9]+)"\)', r'\1\2', py) 538 py = re.sub(rf'Event\(r"{kw}"\)', kw, py) 541 parsed = ast.parse(py, mode='eval')
|
/linux-6.3-rc2/tools/power/pm-graph/ |
A 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
|
A 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 173 %> sudo ./sleepgraph.py -config config/suspend-dev.cfg 291 %> sleepgraph.py -summary . 296 %> sleepgraph.py -summary . -genhtml 335 %> sudo ./sleepgraph.py -config config/suspend.cfg 595 sleepgraph.py on it. 656 [create an output html file using sleepgraph.py] [all …]
|
/linux-6.3-rc2/scripts/kconfig/tests/ |
A D | pytest.ini | 6 # the directory name that contains it. Use __init__.py for all test files. 7 python_files = __init__.py
|
/linux-6.3-rc2/Documentation/userspace-api/netlink/ |
A D | intro-specs.rst | 18 The tool is located at ``tools/net/ynl/cli.py``. It accepts 30 $ ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/ethtool.yaml \ 51 code from ``cli.py``. 78 The code generation itself is performed by ``tools/net/ynl/ynl-gen-c.py``
|
/linux-6.3-rc2/Documentation/trace/ |
A D | events-msr.rst | 35 The trace data can be post processed with the postprocess/decode_msr.py script:: 37 cat /sys/kernel/tracing/trace | decode_msr.py /usr/src/linux/include/asm/msr-index.h
|