Please sign in to comment.
perf: Clarify perf_cpu_context::active_pmu usage by renaming it to ::…
…unique_pmu commit 3f1f33206c16c7b3839d71372bc2ac3f305aa802 upstream. Stephane thought the perf_cpu_context::active_pmu name confusing and suggested using 'unique_pmu' instead. This pointer is a pointer to a 'random' pmu sharing the cpuctx instance, therefore limiting a for_each_pmu loop to those where cpuctx->unique_pmu matches the pmu we get a loop over unique cpuctx instances. Suggested-by: Stephane Eranian <firstname.lastname@example.org> Signed-off-by: Peter Zijlstra <email@example.com> Link: http://firstname.lastname@example.org Signed-off-by: Ingo Molnar <email@example.com> Cc: Li Zefan <firstname.lastname@example.org> Signed-off-by: Greg Kroah-Hartman <email@example.com> (cherry picked from commit 2cd21fa1b54efaf6b5912ef2833fa474fdcf92b7 to fix build failure due to fed4b99)
- Loading branch information...
Showing with 7 additions and 7 deletions.