perf_pmu__ma...uffix_uncore(9)
π perf_pmu__ma...uffix_uncore(9) π
okay bestie, welcome to the Kernel API Manual β¨ this one's a little function with a very long name and a very specific job, and honestly? it ate. let's get into it π«Ά
πΈ NAME πΈ
perf_pmu__match_ignoring_suffix_uncore β so like, the whole question this function is asking is: does the pmu_name match tok if we justβ¦ ignore any trailing suffix on pmu_name and on tok? π lowkey genius. and to be clear, that suffix has to be in the form tok_{digits}, or tok{digits}. no other silliness allowed, ok? π
β¨ SYNOPSIS β¨
bool perf_pmu__match_ignoring_suffix_uncore (const char *pmu_name ,
const char *tok );
it returns a bool, it takes two const char *, and yes that's the whole vibe check π
π ARGUMENTS π
pmu_nameβ thepmu_namein question, and it might have a suffix on the end. might not. we don't judge, we just check πtokβ the possible match forpmu_name. like, the candidate. the one being compared against. the moment of truth fr fr β
π¦ SEE ALSO π¦
the kernel file ./tools/perf/util/pmu.c (that's where the magic lives, iykyk), plus a whole friend group of related functions β go say hi to them:
struct perf_pmu_alias(9)is_sysfs_pmu_core(9)perf_pmu__match_wildcard(9)perf_pmu__match_wildcard_uncore(9)is_pmu_core(9)perf_pmu__name_wildcard_match(9)perf_pmu__name_no_suffix_match(9)
ngl the title up top gets cut off with a ... and that's just how the page rolls β not me doing it, the manpage did that π
and that's the page, bestie!! no notes, 10/10, she understood the assignment π
source path: ./tools/perf/util Β· date: October 2026 Β· page: perf_pmu__ma...uffix_uncore(9) β mwah, that's a wrap πππ
π¦ 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