/Linux-v5.10/tools/perf/tests/ |
D | pmu-events.c | 36 .topic = "branch", 46 .topic = "branch", 56 .topic = "other", 66 .topic = "other", 76 .topic = "other", 94 .topic = "uncore", 106 .topic = "uncore", 188 if (!is_same(table->topic, te->topic)) { in test_pmu_event_table() 190 table->name, table->topic, in test_pmu_event_table() 191 te->topic); in test_pmu_event_table() [all …]
|
/Linux-v5.10/tools/perf/util/ |
D | pmu.c | 264 perf_pmu_assign_str(old->name, "topic", &old->topic, &newalias->topic); in perf_pmu_update_alias() 282 zfree(&newalias->topic); in perf_pmu_free_alias() 310 char *long_desc, char *topic, in __perf_pmu__new_alias() argument 377 alias->topic = topic ? strdup(topic) : NULL; in __perf_pmu__new_alias() 780 (char *)pe->long_desc, (char *)pe->topic, in pmu_add_cpu_aliases_map() 1411 char *topic; member 1427 if (as->topic && bs->topic) { in cmp_sevent() 1428 int n = strcmp(as->topic, bs->topic); in cmp_sevent() 1478 char *topic = NULL; in print_pmu_events() local 1506 (alias->topic && in print_pmu_events() [all …]
|
D | pmu.h | 63 char *topic; member
|
/Linux-v5.10/tools/perf/pmu-events/ |
D | jevents.c | 293 static char *topic; variable 301 i = asprintf(&tp, "%s", topic); in get_topic() 323 free(topic); in add_topic() 324 topic = strdup(bname); in add_topic() 325 if (!topic) { in add_topic() 335 char *topic; member 350 char *topic = pd->topic; in print_events_table_entry() local 363 fprintf(outfp, "\t.topic = \"%s\",\n", topic); in print_events_table_entry() 1073 .topic = get_topic(), in process_one_file() 1079 free(data.topic); in process_one_file()
|
D | pmu-events.h | 17 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-v5.10/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-v5.10/Documentation/devicetree/bindings/arm/ |
D | juno,scpi.txt | 26 [1] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/apas03s22.html
|
D | arm,scmi.txt | 102 [0] http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/index.html
|
D | arm,scpi.txt | 109 [0] http://infocenter.arm.com/help/topic/com.arm.doc.dui0922b/index.html
|
/Linux-v5.10/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 | 136 :Description: Very nice 92 pages GPL book on the topic of modules 346 topic, preparing the reader to understand next month's 388 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-v5.10/Documentation/filesystems/ |
D | befs.rst | 70 reference on this topic. http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-4.html
|
/Linux-v5.10/Documentation/arm/ |
D | microchip.rst | 205 When collecting nodes for a particular peripheral or topic, the identifier have to
|
/Linux-v5.10/Documentation/kbuild/ |
D | reproducible-builds.rst | 13 general topic. This document covers the various reasons why building
|
/Linux-v5.10/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-v5.10/Documentation/trace/ |
D | stm.rst | 143 * [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0444b/index.html
|
/Linux-v5.10/Documentation/gpu/ |
D | drm-kms-helpers.rst | 346 But it nicely fits into the overall topic of mode setting helper
|
/Linux-v5.10/Documentation/arm64/ |
D | sve.rst | 543 http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055c/IHI0055C_beta_aapcs64.pdf 544 http://infocenter.arm.com/help/topic/com.arm.doc.subset.swdev.abi/index.html
|
/Linux-v5.10/Documentation/riscv/ |
D | pmu.rst | 255 [2] https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/f19TmCNP6yA
|
/Linux-v5.10/Documentation/staging/ |
D | tee.rst | 270 [2] http://infocenter.arm.com/help/topic/com.arm.doc.den0028a/index.html
|
/Linux-v5.10/Documentation/core-api/ |
D | unaligned-memory-access.rst | 114 On a related topic, with the above considerations in mind you may observe
|