1*518413d8SIan RogersWhat: /sys/bus/event_source/devices/<pmu> 2*518413d8SIan RogersDate: 2014/02/24 3*518413d8SIan RogersContact: Linux kernel mailing list <linux-kernel@vger.kernel.org> 4*518413d8SIan RogersDescription: Performance Monitoring Unit (<pmu>) 5*518413d8SIan Rogers 6*518413d8SIan Rogers Each <pmu> directory, for a PMU device, is a name 7*518413d8SIan Rogers optionally followed by an underscore and then either a 8*518413d8SIan Rogers decimal or hexadecimal number. For example, cpu is a 9*518413d8SIan Rogers PMU name without a suffix as is intel_bts, 10*518413d8SIan Rogers uncore_imc_0 is a PMU name with a 0 numeric suffix, 11*518413d8SIan Rogers ddr_pmu_87e1b0000000 is a PMU name with a hex 12*518413d8SIan Rogers suffix. The hex suffix must be more than two 13*518413d8SIan Rogers characters long to avoid ambiguity with PMUs like the 14*518413d8SIan Rogers S390 cpum_cf. 15*518413d8SIan Rogers 16*518413d8SIan Rogers Tools can treat PMUs with the same name that differ by 17*518413d8SIan Rogers suffix as instances of the same PMU for the sake of, 18*518413d8SIan Rogers for example, opening an event. For example, the PMUs 19*518413d8SIan Rogers uncore_imc_free_running_0 and 20*518413d8SIan Rogers uncore_imc_free_running_1 have an event data_read; 21*518413d8SIan Rogers opening the data_read event on a PMU specified as 22*518413d8SIan Rogers uncore_imc_free_running should be treated as opening 23*518413d8SIan Rogers the data_read event on PMU uncore_imc_free_running_0 24*518413d8SIan Rogers and PMU uncore_imc_free_running_1. 25