Home
last modified time | relevance | path

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

12

/kernel/linux/linux-5.10/tools/perf/tests/
Dpmu-events.c36 .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 …]
/kernel/linux/linux-5.10/tools/perf/util/
Dpmu.c264 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()
1428 char *topic; member
1444 if (as->topic && bs->topic) { in cmp_sevent()
1445 int n = strcmp(as->topic, bs->topic); in cmp_sevent()
1495 char *topic = NULL; in print_pmu_events() local
1523 (alias->topic && in print_pmu_events()
[all …]
Dpmu.h64 char *topic; member
/kernel/linux/linux-5.10/tools/perf/pmu-events/
Djevents.c293 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()
Dpmu-events.h17 const char *topic; member
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
/kernel/linux/linux-5.10/Documentation/hwmon/
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
Dscpi-hwmon.rst10 Datasheet: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/index.html
Dltc2990.rst19 - Mike Looijmans <mike.looijmans@topic.nl>
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Djuno,scpi.txt26 [1] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0922b/apas03s22.html
Darm,scmi.txt102 [0] http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/index.html
Darm,scpi.txt109 [0] http://infocenter.arm.com/help/topic/com.arm.doc.dui0922b/index.html
/kernel/linux/linux-5.10/Documentation/process/
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
Dkernel-docs.rst136 :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
/kernel/linux/linux-5.10/Documentation/filesystems/
Dbefs.rst70 reference on this topic. http://www.linuxdocs.org/HOWTOs/Kernel-HOWTO-4.html
/kernel/linux/linux-5.10/Documentation/kbuild/
Dreproducible-builds.rst13 general topic. This document covers the various reasons why building
/kernel/linux/linux-5.10/Documentation/arm/
Dmicrochip.rst205 When collecting nodes for a particular peripheral or topic, the identifier have to
/kernel/linux/linux-5.10/Documentation/maintainer/
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
/kernel/linux/linux-5.10/Documentation/trace/
Dstm.rst143 * [2] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0444b/index.html
/kernel/linux/linux-5.10/Documentation/gpu/
Ddrm-kms-helpers.rst346 But it nicely fits into the overall topic of mode setting helper
/kernel/linux/linux-5.10/Documentation/arm64/
Dsve.rst543 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
/kernel/linux/linux-5.10/Documentation/riscv/
Dpmu.rst255 [2] https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/f19TmCNP6yA
/kernel/linux/linux-5.10/Documentation/staging/
Dtee.rst270 [2] http://infocenter.arm.com/help/topic/com.arm.doc.den0028a/index.html
/kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/
Dprocessor_mmio_stale_data.rst260 …https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/proc…
/kernel/linux/linux-5.10/Documentation/core-api/
Dunaligned-memory-access.rst114 On a related topic, with the above considerations in mind you may observe

12