Home
last modified time | relevance | path

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

/linux/tools/perf/pmu-events/arch/nds32/
H A Dmapfile.csv2 # 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/
H A 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 …]
H A DBuild3 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)
66 $(PMU_EVENTS_C): $(JSON) $(JSON_TEST) $(JEVENTS_PY) $(METRIC_PY) $(METRIC_TEST_LOG) \
/linux/tools/perf/pmu-events/arch/riscv/
H A 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/tools/testing/selftests/net/
H A Dbpf_offload.py146 def tool(name, args, flags, JSON=True, ns="", fail=True, include_stderr=False): argument
148 if JSON:
163 if JSON and len(stdout.strip()) != 0:
173 def bpftool(args, JSON=True, ns="", fail=True, include_stderr=False): argument
174 return tool("bpftool", args, {"json":"-p"}, JSON=JSON, ns=ns,
178 _, progs = bpftool("prog show", JSON=True, ns=ns, fail=True)
192 _, maps = bpftool("map show", JSON=True, ns=ns, fail=True)
236 def ip(args, force=False, JSON=True, ns="", fail=True, include_stderr=False): argument
239 return tool("ip", args, {"json":"-j"}, JSON=JSON, ns=ns,
242 def tc(args, JSON=True, ns="", fail=True, include_stderr=False): argument
[all …]
/linux/tools/bpf/bpftool/Documentation/
H A Dcommon_options.rst15 Generate JSON output. For commands that cannot produce JSON, this option
19 Generate human-readable JSON output. Implies **-j**.
H A Dbpftool-prog.rst202 print to the standard output (as plain text, or JSON if relevant option was
/linux/tools/perf/Documentation/
H A Dperf-data.txt31 Triggers JSON conversion. Specify the JSON filename to output.
H A Dperf-stat.txt637 JSON FORMAT
640 With -j, perf stat is able to print out a JSON format output
H A Dperf-list.txt48 Output in JSON format.
/linux/tools/testing/selftests/tc-testing/creating-testcases/
H A 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/Documentation/devicetree/bindings/
H A Dwriting-schema.rst7 written in a JSON-compatible subset of YAML. YAML is used instead of JSON as it
238 `JSON-Schema Specifications <http://json-schema.org/>`_
240 `Using JSON Schema Book <http://usingjsonschema.com/>`_
/linux/tools/testing/selftests/tc-testing/
H A DREADME5 tdc is a Python script to load tc unit tests from a separate JSON file and
/linux/Documentation/security/
H A Dipe.rst155 through XML, JSON, YAML, etcetera), to allow the policy author to understand