Home
last modified time | relevance | path

Searched refs:identifier (Results 1 – 15 of 15) sorted by relevance

/tools/firewire/
Dnosy-dump.h20 uint32_t identifier:2; member
29 uint32_t identifier:2; member
46 uint32_t identifier:2; member
64 uint32_t identifier:2; member
Dnosy-dump.c765 switch (pp->common.identifier) { in print_packet()
/tools/include/uapi/linux/
Dfscrypt.h111 __u8 identifier[FSCRYPT_KEY_IDENTIFIER_SIZE]; member
/tools/perf/util/
Dstat.h71 bool identifier; member
Dstat.c772 if (config->identifier) in create_perf_stat_counter()
/tools/perf/Documentation/
Dperf-stat.txt592 - optional CPU, core, or socket identifier
615 - core : core identifier (with --per-core)
616 - die : die identifier (with --per-die)
617 - socket : socket identifier (with --per-socket)
618 - node : node identifier (with --per-node)
619 - thread : thread identifier (with --per-thread)
Dperf-inject.txt108 When using perf record in the guest, option --sample-identifier
Djitdump-specification.txt78 * uint64_t code_index: unique identifier for the jitted code (see below)
Dperf.data-file-format.txt78 for a executable file name for a pid. An ELF build id is a unique identifier
Dperf-record.txt357 --sample-identifier::
358 Record the sample identifier i.e. PERF_SAMPLE_IDENTIFIER bit set in
Dperf-config.txt227 content based identifier that, if available, will be inserted in a
Dperf-intel-pt.txt1458 …$ sudo perf record -o guest-sideband-testing-guest-perf.data --sample-identifier --buildid-all --s…
/tools/perf/
Ddesign.txt42 * identifier.
323 __u32 index; /* hardware counter identifier */
Dbuiltin-stat.c2802 stat_config.identifier = !(STAT_RECORD && perf_stat.data.is_pipe); in cmd_stat()
/tools/testing/selftests/net/forwarding/
Dvxlan_bridge_1d.sh585 )"1f:6a:"$( : ICMP request identifier