| /linux/tools/perf/pmu-events/arch/powerpc/ |
| A D | mapfile.csv | 2 # PVR,Version,JSON/file/pathname,Type
6 # Version could be used to track version 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/tools/perf/pmu-events/arch/nds32/ |
| A D | mapfile.csv | 2 # MIDR,Version,JSON/file/pathname,Type
7 # Version could be used to track version of JSON file
9 # JSON/file/pathname is the path to JSON file, relative
|
| /linux/tools/perf/pmu-events/arch/riscv/ |
| A D | mapfile.csv | 2 # 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/tools/perf/pmu-events/ |
| A D | README | 8 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 …]
|
| A D | Build | 3 JSON = $(shell [ -d $(JDIR) ] && \
23 # Locate/process JSON files in pmu-events/arch/
36 $(TEST_EMPTY_PMU_EVENTS_C): $(JSON) $(JSON_TEST) $(JEVENTS_PY) $(METRIC_PY) $(METRIC_TEST_LOG)
44 $(PMU_EVENTS_C): $(JSON) $(JSON_TEST) $(JEVENTS_PY) $(METRIC_PY) $(METRIC_TEST_LOG) $(EMPTY_PMU_EVE…
|
| /linux/tools/testing/selftests/net/ |
| A D | bpf_offload.py | 148 if JSON:
163 if JSON and len(stdout.strip()) != 0:
174 return tool("bpftool", args, {"json":"-p"}, JSON=JSON, ns=ns,
235 return tool("ip", args, {"json":"-j"}, JSON=JSON, ns=ns,
239 return tool("tc", args, {"json":"-p"}, JSON=JSON, ns=ns,
420 force=force, JSON=JSON,
423 def unset_xdp(self, mode, force=False, JSON=True, argument
426 force=force, JSON=JSON,
457 _, out = tc(args, JSON=False)
1255 simA.set_xdp(progA, "offload", JSON=False)
[all …]
|
| /linux/tools/perf/pmu-events/arch/arm64/ |
| A D | mapfile.csv | 2 # MIDR,Version,JSON/file/pathname,Type
7 # Version could be used to track version of JSON file
9 # JSON/file/pathname is the path to JSON file, relative
|
| /linux/tools/bpf/bpftool/Documentation/ |
| A D | common_options.rst | 15 Generate JSON output. For commands that cannot produce JSON, this option
19 Generate human-readable JSON output. Implies **-j**.
|
| A D | bpftool-prog.rst | 189 print to the standard output (as plain text, or JSON if relevant option was
|
| /linux/tools/perf/Documentation/ |
| A D | perf-data.txt | 31 Triggers JSON conversion. Specify the JSON filename to output.
|
| A D | perf-stat.txt | 630 JSON FORMAT
633 With -j, perf stat is able to print out a JSON format output
|
| A D | perf-list.txt | 48 Output in JSON format.
|
| /linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| A D | AddingTestCases.txt | 8 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/Documentation/devicetree/bindings/ |
| A D | writing-schema.rst | 7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it
200 `JSON-Schema Specifications <http://json-schema.org/>`_
202 `Using JSON Schema Book <http://usingjsonschema.com/>`_
|
| /linux/Documentation/userspace-api/netlink/ |
| A D | intro-specs.rst | 44 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/Documentation/networking/ |
| A D | statistics.rst | 42 `ip` supports JSON formatting via the `-j` option.
|
| /linux/tools/testing/selftests/tc-testing/ |
| A D | README | 5 tdc is a Python script to load tc unit tests from a separate JSON file and
|
| /linux/Documentation/dev-tools/kunit/ |
| A D | run_wrapper.rst | 322 - ``--json``: If set, stores the test results in a JSON format and prints to `stdout` or
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-class-firmware-attributes | 459 'status' is a read-only file that returns ASCII text in JSON format reporting
|
| /linux/Documentation/security/ |
| A D | ipe.rst | 155 through XML, JSON, YAML, etcetera), to allow the policy author to understand
|