Home
last modified time | relevance | path

Searched refs:metadata (Results 1 – 10 of 10) sorted by relevance

/tools/perf/util/
Dcs-etm.c64 u64 **metadata; member
131 u64 *metadata; in cs_etm__get_magic() local
137 metadata = inode->priv; in cs_etm__get_magic()
138 *magic = metadata[CS_ETM_MAGIC]; in cs_etm__get_magic()
145 u64 *metadata; in cs_etm__get_cpu() local
151 metadata = inode->priv; in cs_etm__get_cpu()
152 *cpu = (int)metadata[CS_ETM_CPU]; in cs_etm__get_cpu()
383 u64 **metadata = etm->metadata; in cs_etm__set_trace_param_etmv3() local
386 t_params[idx].etmv3.reg_ctrl = metadata[idx][CS_ETM_ETMCR]; in cs_etm__set_trace_param_etmv3()
387 t_params[idx].etmv3.reg_trc_id = metadata[idx][CS_ETM_ETMTRACEIDR]; in cs_etm__set_trace_param_etmv3()
[all …]
/tools/testing/selftests/bpf/progs/
Dstrobemeta.h197 struct strobemeta_payload metadata; member
514 sample_end = read_strobe_meta(task, &sample->metadata); in on_event()
516 sample_end = sample_end ? : &sample->metadata; in on_event()
Dpyperf.h56 int metadata; member
247 bpf_perf_event_output(ctx, &perfmap, 0, event, offsetof(Event, metadata)); in __on_event()
/tools/perf/Documentation/
Dperf-lock.txt27 'perf lock info' shows metadata like threads or addresses
Dperf-top.txt251 the pausing used in this technique is leading to loss of metadata events such
Dintel-pt.txt622 The v4.2 kernel introduced support for a context switch metadata event,
629 switches") commit, that introduces these metadata events for further info.
648 decoding in kernels where the PERF_RECORD_SWITCH metadata event isn't
Dperf.data-file-format.txt8 On a high level perf.data contains the events generated by the PMUs, plus metadata.
/tools/testing/selftests/net/forwarding/
Ddevlink_lib.sh247 local metadata=$1; shift
250 | jq -e '.[][][].metadata | contains(["'$metadata'"])' \
/tools/objtool/Documentation/
Dstack-validation.txt1 Compile-time stack metadata validation
10 analyzes every .o file and ensures the validity of its stack metadata.
28 Why do we need stack metadata validation?
31 Here are some of the benefits of validating stack metadata:
128 callable function in order to analyze its stack metadata.
/tools/testing/selftests/seccomp/
Dseccomp_bpf.c2293 struct __test_metadata *metadata; member
2359 self->sibling[0].metadata = _metadata; in FIXTURE_SETUP()
2367 self->sibling[1].metadata = _metadata; in FIXTURE_SETUP()