| /Linux-v6.1/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 | 248 self.topic = ''
335 def read_json_events(path: str, topic: str) -> Sequence[JsonEvent]:
344 event.topic = topic
352 for event in read_json_events(item.path, topic=''):
366 def add_events_table_entries(item: os.DirEntry, topic: str) -> None:
370 for e in read_json_events(item.path, topic):
383 return (j.desc is not None, fix_none(j.topic), fix_none(j.name), fix_none(j.pmu),
398 def get_topic(topic: str) -> str:
399 if topic.endswith('metrics.json'):
401 return removesuffix(topic, '.json').replace('-', ' ')
[all …]
|
| D | pmu-events.h | 20 const char *topic; member
|
| 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
|
| /Linux-v6.1/tools/perf/tests/ |
| D | pmu-events.c | 48 .topic = "branch",
59 .topic = "branch",
70 .topic = "other",
81 .topic = "other",
92 .topic = "other",
104 .topic = "cache",
125 .topic = "uncore",
139 .topic = "uncore",
153 .topic = "uncore",
167 .topic = "uncore",
[all …]
|
| /Linux-v6.1/drivers/misc/habanalabs/common/ |
| D | memory_mgr.c | 166 behavior->topic, rc); in hl_mmap_mem_buf_alloc()
178 behavior->topic, rc); in hl_mmap_mem_buf_alloc()
258 buf->behavior->topic, user_mem_size, buf->mappable_size);
271 buf->behavior->topic, vma->vm_start);
280 buf->behavior->topic);
333 const char *topic; local
339 topic = buf->behavior->topic;
343 topic, id);
|
| D | command_buffer.c | 255 .topic = "CB",
|
| /Linux-v6.1/tools/perf/util/ |
| D | pmu.c | 268 perf_pmu_assign_str(old->name, "topic", &old->topic, &newalias->topic); in perf_pmu_update_alias()
286 zfree(&newalias->topic); in perf_pmu_free_alias()
325 char *long_desc = NULL, *topic = NULL, *unit = NULL, *perpkg = NULL, in __perf_pmu__new_alias() local
331 topic = (char *)pe->topic; in __perf_pmu__new_alias()
395 alias->topic = topic ? strdup(topic) : NULL; in __perf_pmu__new_alias()
1573 char *topic; member
1590 if (as->topic && bs->topic) { in cmp_sevent()
1591 int n = strcmp(as->topic, bs->topic); in cmp_sevent()
1663 char *topic = NULL; in print_pmu_events() local
1697 (alias->topic && in print_pmu_events()
[all …]
|
| D | pmu.h | 78 char *topic; member
|
| /Linux-v6.1/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.1/Documentation/process/ |
| 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 | 90 :Description: A very nice GPL book on the topic of modules
358 topic, preparing the reader to understand next month's
400 different situations. We also investigate the complex topic of
|
| D | stable-api-nonsense.rst | 104 This is a much more "volatile" topic if you talk to people who try to
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | befs.rst | 70 reference on this topic. http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-4.html
|
| /Linux-v6.1/Documentation/arm/ |
| D | microchip.rst | 225 When collecting nodes for a particular peripheral or topic, the identifier have to
|
| /Linux-v6.1/Documentation/kbuild/ |
| D | reproducible-builds.rst | 13 general topic. This document covers the various reasons why building
|
| /Linux-v6.1/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.1/Documentation/trace/ |
| D | stm.rst | 143 * [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0444b/index.html
|
| /Linux-v6.1/Documentation/gpu/ |
| D | drm-kms-helpers.rst | 373 But it nicely fits into the overall topic of mode setting helper
|
| /Linux-v6.1/Documentation/staging/ |
| D | tee.rst | 300 [2] http://infocenter.arm.com/help/topic/com.arm.doc.den0028a/index.html
|
| /Linux-v6.1/Documentation/arm64/ |
| D | sve.rst | 611 http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055c/IHI0055C_beta_aapcs64.pdf
612 http://infocenter.arm.com/help/topic/com.arm.doc.subset.swdev.abi/index.html
|
| /Linux-v6.1/Documentation/admin-guide/hw-vuln/ |
| D | processor_mmio_stale_data.rst | 260 …https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/proc…
|
| /Linux-v6.1/Documentation/core-api/ |
| D | unaligned-memory-access.rst | 114 On a related topic, with the above considerations in mind you may observe
|
