| /Linux-v6.6/tools/perf/pmu-events/ |
| D | empty-pmu-events.c | 19 .topic = "cache",
26 .topic = "other",
32 .topic = "other",
38 .topic = "other",
44 .topic = "uncore",
52 .topic = "uncore",
60 .topic = "uncore",
68 .topic = "uncore",
76 .topic = "uncore",
84 .topic = "uncore",
[all …]
|
| D | jevents.py | 302 self.topic = ''
404 def read_json_events(path: str, topic: str) -> Sequence[JsonEvent]:
413 event.topic = topic
431 for event in read_json_events(item.path, topic=''):
438 def add_events_table_entries(item: os.DirEntry, topic: str) -> None:
440 for e in read_json_events(item.path, topic):
456 … return (fix_none(j.pmu).replace(',','_'), fix_none(j.name), j.desc is not None, fix_none(j.topic),
558 def get_topic(topic: str) -> str:
559 if topic.endswith('metrics.json'):
561 return removesuffix(topic, '.json').replace('-', ' ')
[all …]
|
| D | README | 26 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
|
| D | pmu-events.h | 46 const char *topic; member
|
| /Linux-v6.6/tools/perf/tests/ |
| D | pmu-events.c | 51 .topic = "branch",
63 .topic = "branch",
75 .topic = "other",
87 .topic = "other",
99 .topic = "other",
112 .topic = "cache",
133 .topic = "uncore",
147 .topic = "uncore",
161 .topic = "uncore",
175 .topic = "uncore",
[all …]
|
| /Linux-v6.6/drivers/accel/habanalabs/common/ |
| D | memory_mgr.c | 165 behavior->topic, rc); in hl_mmap_mem_buf_alloc()
177 behavior->topic, rc); in hl_mmap_mem_buf_alloc()
257 buf->behavior->topic, user_mem_size, buf->mappable_size);
270 buf->behavior->topic, vma->vm_start);
279 buf->behavior->topic);
332 const char *topic; local
338 topic = buf->behavior->topic;
342 topic, id);
|
| D | command_buffer.c | 259 .topic = "CB",
|
| /Linux-v6.6/tools/perf/ |
| D | builtin-list.c | 98 static void default_print_event(void *ps, const char *pmu_name, const char *topic, in default_print_event() argument
117 (!topic || !strglobmatch_nocase(topic, print_state->event_glob))) in default_print_event()
128 if (strcmp(print_state->last_topic, topic ?: "")) { in default_print_event()
129 if (topic) in default_print_event()
130 printf("\n%s:\n", topic); in default_print_event()
132 print_state->last_topic = strdup(topic ?: ""); in default_print_event()
140 if (!topic && event_type_desc) { in default_print_event()
324 static void json_print_event(void *ps, const char *pmu_name, const char *topic, in json_print_event() argument
342 if (topic) { in json_print_event()
343 fix_escape_printf(&buf, "%s\t\"Topic\": \"%S\"", need_sep ? ",\n" : "", topic); in json_print_event()
|
| /Linux-v6.6/tools/perf/util/ |
| D | pfm.c | 179 char topic[80], name[80]; in print_libpfm_event() local
184 snprintf(topic, sizeof(topic), "pfm %s", pinfo->name); in print_libpfm_event()
223 print_cb->print_event(print_state, pinfo->name, topic, in print_libpfm_event()
258 topic, in print_libpfm_event()
|
| D | pmus.c | 353 const char *topic; member
370 ret = strcmp(as->topic ?: "", bs->topic ?: ""); in cmp_sevent()
426 COPY_STR(topic); in perf_pmus__print_pmu_events__callback()
477 aliases[j].topic, in perf_pmus__print_pmu_events()
492 zfree(&aliases[j].topic); in perf_pmus__print_pmu_events()
|
| D | pmu.c | 53 char *topic; member
405 zfree(&newalias->topic); in perf_pmu_free_alias()
484 assign_str(pe->name, "topic", &data->alias->topic, pe->topic); in update_alias()
506 const char *long_desc = NULL, *topic = NULL, *unit = NULL, *pmu_name = NULL; in perf_pmu__new_alias() local
516 topic = pe->topic; in perf_pmu__new_alias()
545 alias->topic = topic ? strdup(topic) : NULL; in perf_pmu__new_alias()
1699 info.topic = event->topic; in perf_pmu__for_each_event()
1715 info.topic = NULL; in perf_pmu__for_each_event()
|
| D | print-events.h | 14 void (*print_event)(void *print_state, const char *topic,
|
| D | pmu.h | 184 const char *topic; member
|
| /Linux-v6.6/Documentation/process/ |
| D | maintainer-kvm-x86.rst | 38 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 …]
|
| D | 7.AdvancedTopics.rst | 61 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
|
| D | kernel-docs.rst | 71 :Description: A very nice GPL book on the topic of modules
|
| /Linux-v6.6/Documentation/hwmon/ |
| D | vexpress.rst | 15 - 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
|
| D | scpi-hwmon.rst | 10 Datasheet: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/index.html
|
| D | ltc2990.rst | 19 - Mike Looijmans <mike.looijmans@topic.nl>
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | befs.rst | 70 reference on this topic. http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-4.html
|
| /Linux-v6.6/Documentation/arch/arm/ |
| D | microchip.rst | 225 When collecting nodes for a particular peripheral or topic, the identifier have to
|
| /Linux-v6.6/Documentation/kbuild/ |
| D | reproducible-builds.rst | 13 general topic. This document covers the various reasons why building
|
| /Linux-v6.6/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 100 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-v6.6/Documentation/trace/ |
| D | stm.rst | 143 * [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0444b/index.html
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | locking.txt | 223 please read up on that topic in litmus-tests.txt.
|
