metricgroup_..._metric_list(9)
β¨ metricgroup__add_metric_list π
okay so bestie, welcome to the Kernel API Manual π β this one's <pink>metricgroup__add_metric_list(9)</pink>, and no cap it's giving "find the metrics you asked for and actually add them" energy. Let's get into it π«Ά
πΈ NAME πΈ
metricgroup__add_metric_list β Find and add metrics, or metric groups, specified in a list. Literally its whole job π
π¦ SYNOPSIS π¦
int metricgroup__add_metric_list (const char *pmu , const char *list ,
bool metric_no_group , bool metric_no_threshold , const char
*user_requested_cpu_list , bool system_wide , struct list_head
*metric_list , const struct pmu_metrics_table *table );
it returns an int, bestie β write it down π
β ARGUMENTS β
pmuβ a pmu to restrict the metrics to, or"all"for all PMUS. like,"all"is the main character option here πlistβ the list of metrics or metric groups. For example,"IPC,CPI,TopDownL1"would match theIPCandCPImetrics, andTopDownL1would match all the metrics in theTopDownL1group. soTopDownL1is out here collecting the whole group, iconic πmetric_no_groupβ should events written to events be grouped"{}"or global. Grouping is the default but due to multiplexing the user may override. yeah β default is grouping, but multiplexing exists so the user gets to override, iykyk πmetric_no_thresholdβ-- undescribed --. that's it. that's the description. the docs literally said nothing on this one ππ we're not gonna invent lore for it, moving onuser_requested_cpu_listβ Command line specified CPUs to record on. so, the cpus you asked for from the command line π§system_wideβ Are events for all processes recorded. yes this is phrased as a question. yes it's still the argument πmetric_listβ The list that metrics are added to. this is where the good stuff goes πtableβ The table that is searched for metrics, most commonly the table for the architecture perf is running upon. so like, the arch table for whatever perf is running on π¦
π SEE ALSO π
setup_metric_events(9)resolve_metric(9)__add_metric(9)metric_list_cmp(9)default_metricgroup_cmp(9)metricgroup__add_metric(9)find_tool_events(9)build_combined_expr_ctx(9)parse_ids(9)
and also the kernel file ./tools/perf/util/metricgroup.c β literally the source, go read it, it's serving context π
π«Ά quick reminder bestie: themetric_no_thresholddescription is<red>genuinely listed as-- undescribed --in the original. that's not me being lazy, that's Just What It Says. keep that energy.
and that's the whole page!! mwah π this one ships from ./tools/perf/util, dated October 2026, filed under metricgroup_..._metric_list(9) β slay, go add some metrics β¨ππ₯
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms