Searched refs:JSON (Results 1 – 13 of 13) sorted by relevance
| /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 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 of JSON file
9 # 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 | 7 JSON = $(shell [ -d $(JDIR) ] && \
14 # Locate/process JSON files in pmu-events/arch/
17 $(OUTPUT)pmu-events/pmu-events.c: $(JSON) $(JSON_TEST) $(JEVENTS)
|
| /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 of JSON file
9 # JSON/file/pathname is the path to JSON file, relative
|
| /linux/tools/testing/selftests/bpf/ |
| A D | test_offload.py | 145 if JSON:
158 if JSON and len(stdout.strip()) != 0:
169 return tool("bpftool", args, {"json":"-p"}, JSON=JSON, ns=ns,
228 return tool("ip", args, {"json":"-j"}, JSON=JSON, ns=ns,
232 return tool("tc", args, {"json":"-p"}, JSON=JSON, ns=ns,
482 force=force, JSON=JSON,
485 def unset_xdp(self, mode, force=False, JSON=True, argument
488 force=force, JSON=JSON,
519 _, out = tc(args, JSON=False)
1317 simA.set_xdp(progA, "offload", JSON=False)
[all …]
|
| /linux/tools/bpf/bpftool/Documentation/ |
| A D | common_options.rst | 13 Generate JSON output. For commands that cannot produce JSON, this
17 Generate human-readable JSON output. Implies **-j**.
|
| A D | bpftool-prog.rst | 188 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.
|
| /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
173 `JSON-Schema Specifications <http://json-schema.org/>`_
175 `Using JSON Schema Book <http://usingjsonschema.com/>`_
|
| /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/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
|
Completed in 20 milliseconds