[P9,POwer NV] Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice when perf stat is done (perf:)

[bugproxy]

== Comment: #0 - Sukadev Bhattiprolu - 2017-09-01 12:56:47 ==

---Problem Description---
Problem description :
=============
Perf PMU event : pm_br_2path and pm_ld_miss_l1 is counted twice , it is because two raw point to the same name.

[
  {,
    "EventCode": "0x20036",
    "EventName": "PM_BR_2PATH",
    "BriefDescription": "Branches that are not strongly biased",
    "PublicDescription": ""
  },
  {,
    "EventCode": "0x40036",
    "EventName": "PM_BR_2PATH",
    "BriefDescription": "Branches that are not strongly biased",
    "PublicDescription": ""
  },

Ex :
===

[root@zzfp189p1 ~]# perf stat -e pm_br_2path sleep 1

 Performance counter stats for 'sleep 1':

            30,163 pm_br_2path
     <not counted> pm_br_2path (0.00%)

       1.002046416 seconds time elapsed

[root@zzfp189p1 ~]# perf stat -e pm_ld_miss_l1 sleep 1

 Performance counter stats for 'sleep 1':

             9,217 pm_ld_miss_l1
     <not counted> pm_ld_miss_l1 (0.00%)

       1.001956110 seconds time elapsed

---Steps to Reproduce---
 Steps to reproduce :
============
1. Install perf (linux-tools)
2. Run
    perf stat -e pm_ld_miss_l1 sleep 1
    perf stat -e pm_br_2path sleep 1

== Comment: #1 - Sukadev Bhattiprolu - 2017-09-01 12:58:16 ==
The fix for this bug was pulled into Arnaldo's tree:

https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=perf/core&id=828e291e2982a7c10a62aa32195d0cb501cedaae

[Joseph Salisbury (jsalisbury)]

Can you post a link here when this patch gets pulled into linux-next or mainline?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-05 17:51 EDT-------
The patch was merged into perf-tip by Ingo Molnar, here:

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit?id=770e96125515daf1c7bc179323f2e0d488dfe6ac

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 4.13.0-11.12

---------------
linux (4.13.0-11.12) artful; urgency=low

  * linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)

  * kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
    - s390/mm: fix local TLB flushing vs. detach of an mm address space
    - s390/mm: fix race on mm->context.flush_mm

  * CVE-2017-1000251
    - Bluetooth: Properly check L2CAP config option output buffer length

 -- Seth Forshee <email address hidden> Tue, 12 Sep 2017 10:18:38 -0500