Home
last modified time | relevance | path

Searched refs:topic (Results 1 – 25 of 48) sorted by relevance

12

/linux/tools/perf/tests/
H A Dpmu-events.c49 .topic = "branch",
59 .topic = "branch",
69 .topic = "other",
79 .topic = "other",
89 .topic = "other",
100 .topic = "cache",
120 .topic = "uncore",
131 .topic = "uncore",
142 .topic = "uncore",
153 .topic = "uncore",
[all …]
/linux/tools/perf/
H A Dbuiltin-list.c118 static void default_print_event(void *ps, const char *topic, in default_print_event() argument
142 (!topic || !strglobmatch_nocase(topic, print_state->event_glob))) in default_print_event()
153 if (strcmp(print_state->last_topic, topic ?: "")) { in default_print_event()
154 if (topic) in default_print_event()
155 fprintf(fp, "\n%s:\n", topic); in default_print_event()
157 print_state->last_topic = strdup(topic ?: ""); in default_print_event()
165 if (!topic && event_type_desc) { in default_print_event()
363 static void json_print_event(void *ps, const char *topic, in json_print_event() argument
390 (!topic || !strglobmatch_nocase(topic, print_state->common.event_glob))) in json_print_event()
400 if (topic) { in json_print_event()
[all …]
/linux/tools/perf/pmu-events/
H A Djevents.py333 self.topic = ''
461 def read_json_events(path: str, topic: str) -> Sequence[JsonEvent]:
470 event.topic = topic
490 for event in read_json_events(item.path, topic=''):
499 def add_events_table_entries(item: os.DirEntry, topic: str) -> None:
501 for e in read_json_events(item.path, topic):
518 … return (fix_none(j.pmu).replace(',','_'), fix_none(j.name), j.desc is not None, fix_none(j.topic),
624 def get_topic(topic: str) -> str:
625 if topic.endswith('metrics.json'):
627 return removesuffix(topic, '.json').replace('-', ' ')
[all …]
H A DREADME26 such as Pipelining, Cache, Memory, Floating-point etc. All events for a topic
28 the topic. Eg: "Floating-point.json".
30 All the topic JSON files for a CPU model/family should be in a separate
H A Dpmu-events.h52 const char *topic; member
H A Dempty-pmu-events.c2863 pe->topic = (*p == '\0' ? NULL : p); in decompress_event()
/linux/tools/perf/util/
H A Dpfm.c189 char topic[80], name[80]; in print_libpfm_event() local
194 snprintf(topic, sizeof(topic), "pfm %s", pinfo->name); in print_libpfm_event()
233 print_cb->print_event(print_state, topic, pinfo->name, in print_libpfm_event()
268 topic, in print_libpfm_event()
H A Dpmus.c520 const char *topic; member
538 ret = strcmp(as->topic ?: "", bs->topic ?: ""); in cmp_sevent()
595 COPY_STR(topic); in perf_pmus__print_pmu_events__callback()
646 aliases[j].topic, in perf_pmus__print_pmu_events()
664 zfree(&aliases[j].topic); in perf_pmus__print_pmu_events()
H A Dprint-events.h14 void (*print_event)(void *print_state, const char *topic,
H A Dpmu.c69 char *topic; member
441 zfree(&alias->topic); in perf_pmu_free_alias()
550 assign_str(pe->name, "topic", &data->alias->topic, pe->topic); in update_alias()
589 const char *long_desc = NULL, *topic = NULL, *unit = NULL, *pmu_name = NULL; in perf_pmu__new_alias() local
599 topic = pe->topic; in perf_pmu__new_alias()
654 alias->topic = topic ? strdup(topic) : NULL; in perf_pmu__new_alias()
2292 info.topic = event->topic; in perf_pmu__for_each_event()
2306 info.topic = NULL; in perf_pmu__for_each_event()
H A Dpmu.h229 const char *topic; member
H A Ddrm_pmu.c288 .topic = "drm", in drm_pmu__for_each_event()
/linux/Documentation/process/
H A Dmaintainer-kvm-x86.rst38 The KVM x86 tree is organized into multiple topic branches. The purpose of
39 using finer-grained topic branches is to make it easier to keep tabs on an area
41 commits, e.g. dropping the HEAD commit of a topic branch has no impact on other
43 delays only that topic branch.
45 All topic branches, except for ``next`` and ``fixes``, are rolled into ``next``
46 via a Cthulhu merge on an as-needed basis, i.e. when a topic branch is updated.
55 requests (from KVM x86 to main KVM) are sent for each KVM x86 topic branch,
57 following rc7 for "normal" releases. If all goes well, the topic branches are
94 select a specific topic branch as the base. If there are conflicts and/or
95 dependencies across topic branches, it is the maintainer's job to sort them
[all …]
H A D7.AdvancedTopics.rst61 of development can be separated into a separate "topic branch" and
118 thing happening; putting up a git tree with unreviewed or off-topic patches
131 branch stick closely to the associated topic; a "driver fixes" branch
/linux/Documentation/hwmon/
H A Dvexpress.rst15 - http://infocenter.arm.com/help/topic/com.arm.doc.subset.boards.express/index.html
19 - http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0447-/index.html
H A Dscpi-hwmon.rst10 Datasheet: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/index.html
H A Dltc2990.rst19 - Mike Looijmans <mike.looijmans@topic.nl>
/linux/Documentation/filesystems/
H A Dbefs.rst70 reference on this topic. http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-4.html
/linux/Documentation/arch/arm/
H A Dmicrochip.rst225 When collecting nodes for a particular peripheral or topic, the identifier have to
/linux/Documentation/maintainer/
H A Drebasing-and-merging.rst100 which may contain multiple topic branches; each branch is usually developed
200 creating a topic branch dedicated to the prerequisite commits that can be
/linux/Documentation/tee/
H A Dop-tee.rst157 [2] http://infocenter.arm.com/help/topic/com.arm.doc.den0028a/index.html
/linux/drivers/accel/habanalabs/common/
H A Dcommand_buffer.c259 .topic = "CB",
/linux/Documentation/admin-guide/hw-vuln/
H A Dindirect-target-selection.rst166 .. [#f2] Affected Processors list - https://www.intel.com/content/www/us/en/developer/topic-technol…
/linux/Documentation/trace/
H A Dstm.rst143 * [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0444b/index.html
/linux/tools/memory-model/Documentation/
H A Dlocking.txt228 please read up on that topic in litmus-tests.txt.

12