perf_pmu__m...dcard_uncore(9)

💅 perf_pmu__match_wildcard_uncore(9) — Kernel API Manual, but make it make sense

okay bestie, strap in 🎀 this one lives in the Kernel API Manual, and it's literally just one job: figure out if some little string matches a PMU's name. That's it. That's the whole vibe check. ✨

---

🌸 NAME 🌸

perf_pmu__match_wildcard_uncore — the function that answers the question does to_match match the PMU's name? 👀 (spoiler: it's giving "yes or no", and it returns a bool, so like… no hedging, no maybes, no "it's complicated" 💀)

---

✨ SYNOPSIS ✨

bool perf_pmu__match_wildcard_uncore (const char *pmu_name , const char *to_match );

two const char *s walk in, a bool walks out. iconic behavior honestly 🫶

---

🦋 ARGUMENTS 🦋

• pmu_name — this one is the pmu->name or the pmu->alias, i.e. the thing you're matching against. your reference point. your main character, if you will 👑
• to_match — this is the json struct pmu_event name. and here's the tea 🍓: it may lack a suffix, and if it does, that totally matches. OR it can be shaped like "socket,pmuname", which will match "socketX_pmunameY" — so the comma-socket form expands out into the real socketX_pmunameY shape and goes slay, we match 💖

ngl the comma form is the sneaky one — read it twice, it's not doing what your first glance thinks it's doing 🙈

---

🔥 SEE ALSO 🔥

the whole friend group 🫶 go check out:

• Kernel file ./tools/perf/util/pmu.c
• struct perf_pmu_alias(9)
• is_sysfs_pmu_core(9)
• perf_pmu__match_wildcard(9)
• perf_pmu__match_ignoring_suffix_uncore(9)
• is_pmu_core(9)
• perf_pmu__name_wildcard_match(9)
• perf_pmu__name_no_suffix_match(9)

---

that's the whole page, bestie, no notes 🌈 this came out of ./tools/perf/util, dated October 2026 — and yes we're still out here matching wildcards uncore-style, periodt 💅💜