perf: POWER8: Allow specifying Power PMU events by name rather than raw codes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Leann Ogasawara | ||
Zesty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
== Comment: #0 - Sukadev Bhattiprolu <email address hidden> - 2015-10-19 20:45:40 ==
Power processor provides the ability to monitor a large number of Performance
Monitoring events. However the linux kernel/perf tool requires that a vast majority
of these events be specified by their raw codes:
perf stat -e r100f2 sleep 1
We would instead like to be able to specify the events by its name:
perf stat -e pm_1plus_ppc_cmpl sleep 1
where the event name name 'pm_1plus_ppc_cmpl' is defined in
the POWER PMU specs
== Comment: #1 - Sukadev Bhattiprolu 2015-10-27 13:43:20 ==
Here is a pointer to a newer version of the patch set:
https:/
== Comment: #10 - Sukadev Bhattiprolu - 2016-03-01 13:50:37 ==
(In reply to comment #9)
> any change in upstream status? If not, should we re-target this to 16.04.1
> and 16.10?
No, no comments yet from maintainer, so patches still stuck. Yes we could
re-target to 16.10 for now.
tags: | added: architecture-ppc64 bugnameltc-132028 severity-medium targetmilestone-inin1604 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
tags: |
added: targetmilestone-inin1610 removed: targetmilestone-inin1604 |
tags: |
added: targetmilestone-inin1704 removed: targetmilestone-inin1610 |
tags: |
added: targetmilestone-inin1610 removed: targetmilestone-inin1704 |
tags: |
added: targetmilestone-inin1704 removed: targetmilestone-inin1610 |
tags: | added: cscc |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1553178/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]