Home
last modified time | relevance | path

Searched refs:JSON (Results 1 – 19 of 19) sorted by relevance

/linux-6.6.21/tools/perf/pmu-events/arch/powerpc/
Dmapfile.csv2 # PVR,Version,JSON/file/pathname,Type
6 # Version could be used to track version of of JSON file
8 # JSON/file/pathname is the path to JSON file, relative
12 # Multiple PVRs could map to a single JSON file.
/linux-6.6.21/tools/perf/pmu-events/arch/nds32/
Dmapfile.csv2 # MIDR,Version,JSON/file/pathname,Type
7 # Version could be used to track version of of JSON file
9 # JSON/file/pathname is the path to JSON file, relative
/linux-6.6.21/tools/perf/pmu-events/arch/riscv/
Dmapfile.csv2 # MVENDORID-MARCHID-MIMPID,Version,JSON/file/pathname,Type
9 # Version could be used to track version of JSON file
11 # JSON/file/pathname is the path to JSON file, relative
/linux-6.6.21/tools/perf/pmu-events/
DREADME8 The 'jevents' program tries to locate and process JSON files in the directory
12 JSON files, each of which describes a set of PMU events.
19 - To reduce JSON event duplication per architecture, platform JSONs may
27 should be placed in a separate JSON file - where the file name identifies
30 All the topic JSON files for a CPU model/family should be in a separate
41 Using the JSON files and the mapfile, 'jevents' generates the C source file,
45 (one table like the following, per JSON file; table name 'pme_power8'
46 is derived from JSON file name, 'power8.json').
80 JSON file. Hence several entries in the pmu_events_map[] could map
137 is the pathname to the directory containing the CPU's JSON
[all …]
DBuild3 JSON = $(shell [ -d $(JDIR) ] && \
21 # Locate/process JSON files in pmu-events/arch/
34 $(PMU_EVENTS_C): $(JSON) $(JSON_TEST) $(JEVENTS_PY) $(METRIC_PY) $(METRIC_TEST_LOG)
/linux-6.6.21/tools/testing/selftests/bpf/
Dtest_offload.py143 def tool(name, args, flags, JSON=True, ns="", fail=True, include_stderr=False): argument
145 if JSON:
158 if JSON and len(stdout.strip()) != 0:
168 def bpftool(args, JSON=True, ns="", fail=True, include_stderr=False): argument
169 return tool("bpftool", args, {"json":"-p"}, JSON=JSON, ns=ns,
173 _, progs = bpftool("prog show", JSON=True, ns=ns, fail=True)
185 _, maps = bpftool("map show", JSON=True, ns=ns, fail=True)
225 def ip(args, force=False, JSON=True, ns="", fail=True, include_stderr=False): argument
228 return tool("ip", args, {"json":"-j"}, JSON=JSON, ns=ns,
231 def tc(args, JSON=True, ns="", fail=True, include_stderr=False): argument
[all …]
/linux-6.6.21/tools/perf/pmu-events/arch/arm64/
Dmapfile.csv2 # MIDR,Version,JSON/file/pathname,Type
7 # Version could be used to track version of of JSON file
9 # JSON/file/pathname is the path to JSON file, relative
/linux-6.6.21/tools/bpf/bpftool/Documentation/
Dcommon_options.rst16 Generate JSON output. For commands that cannot produce JSON, this
20 Generate human-readable JSON output. Implies **-j**.
Dbpftool-prog.rst205 output (as plain text, or JSON if relevant option was
/linux-6.6.21/tools/perf/Documentation/
Dperf-data.txt31 Triggers JSON conversion. Specify the JSON filename to output.
Dperf-stat.txt607 JSON FORMAT
610 With -j, perf stat is able to print out a JSON format output
Dperf-list.txt48 Output in JSON format.
/linux-6.6.21/Documentation/devicetree/bindings/
Dwriting-schema.rst7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it
175 `JSON-Schema Specifications <http://json-schema.org/>`_
177 `Using JSON Schema Book <http://usingjsonschema.com/>`_
/linux-6.6.21/tools/testing/selftests/tc-testing/creating-testcases/
DAddingTestCases.txt8 User-defined tests should be added by defining a separate JSON file. This
10 template.json for the required JSON format for test cases.
22 Be aware of required escape characters in the JSON data - particularly
/linux-6.6.21/Documentation/userspace-api/netlink/
Dintro-specs.rst44 The input arguments are parsed as JSON, while the output is only
46 be expressed as JSON directly. If such attributes are needed in
/linux-6.6.21/Documentation/networking/
Dstatistics.rst42 `ip` supports JSON formatting via the `-j` option.
/linux-6.6.21/tools/testing/selftests/tc-testing/
DREADME5 tdc is a Python script to load tc unit tests from a separate JSON file and
/linux-6.6.21/Documentation/dev-tools/kunit/
Drun_wrapper.rst322 - ``--json``: If set, stores the test results in a JSON format and prints to `stdout` or
/linux-6.6.21/Documentation/ABI/testing/
Dsysfs-class-firmware-attributes429 'status' is a read-only file that returns ASCII text in JSON format reporting