Setting this to Fix Released for Zesty 17.04 and newer since the patches
landed upstream in v4.9 and v4.10:
867a979a83d38fb82c4e7534a0281a02ef1700a3
v4.9-rc1~63^2~1^2~17
80eeb67fe577aa76b2d1bb5b029bca097f0f25bc
v4.9-rc1~63^2~1^2~16
933f82ff72d7d1641663462f61f3056ee1fe3f8b
v4.9-rc1~63^2~1^2~15
ce88f27ccc724fa8e6766fdd4140768931f42f88
v4.9-rc1~63^2~1^2~14
f33d1227197e0fe9d3682c5a766fdc74559da78e
v4.9-rc1~63^2~1^2~13
dc720ffc9863b618a192f5949234c54aad00ed24
v4.9-rc1~63^2~1^2~12
08e60ed15d0483be38a87d17538ccf02acff5b1f
v4.9-rc1~63^2~1^2~11
61eb2eb434b3430c6ef70536eb3d16b616b5ee52
v4.9-rc1~63^2~1^2~10
1c5f01fe8660fc48625a94a5ed10e4dbaea95d5f
v4.9-rc1~63^2~1^2~9
fc06e2a5aad9fcf7efaabd7550ac31f648d2f2bc
v4.9-rc1~63^2~1^2~8
794ba54a8393456d503958d6217874e455b6a771
v4.9-rc1~63^2~1^2~7
c8d6828a6510c9363180ebf662b51d032e0eb85a
v4.9-rc1~63^2~1^2~6
dd5f10368a5f27ec926395056d959513ca4578cc
v4.9-rc1~63^2~1^2~5
06d839b4f712065d76cba92e7e10e9d771771c5a
v4.9-rc1~63^2~1^2~4
06835545b144cab6e7748748576145ea15f68dff
v4.9-rc1~63^2~1^2~3
e312bcf13053970c0f07ec2c02d7d9be1a036ce0
v4.9-rc1~63^2~1^2~2
0b1db474314c883d0bfc6720278667a6155e995a
v4.9-rc1~63^2~1^2~1
b42c7369e3f451e22c2b0be5d193955498d37546
v4.9-rc1~63^2~1^2
72c6ff2583fba824dc38c0ce87b838631cdb8294
v4.9-rc1~63^2^2~8
27b565b1eb04a277027953cab13b5aad5d469390
v4.10-rc1~190^2~14^2~20
b74d1315cab113ce1e0ee5e10eb6638219c1b0d1
v4.10-rc1~190^2~14^2~19
19c0389b60d486010d508d5a1551ee9b6a8b2f45
v4.10-rc1~190^2~14^2~18
052aa3cce3f2b91e339318e5fe9806d0cfd822f0
v4.10-rc1~190^2~14^2~17
4a00680b059a6c2c378945e2dffa2fa2876a4fc1
v4.10-rc1~190^2~14^2~16
dcfbad10c7ba0bd2f4993c8d8a258471eb6083ff
v4.10-rc1~190^2~14^2~15
ede007404388cd1ba306760a2881dc9722f5bb47
v4.10-rc1~190^2~14^2~14
4b90798ebb0bab8fe1ed9065e80879503f5601d2
v4.10-rc1~190^2~14^2~13
d910f0ba6d72a0917ae30b6aed5131988e3096e4
v4.10-rc1~190^2~14^2~12
902ea4ee33e6dccece0f78a68e882eee9be9577f
v4.10-rc1~190^2~14^2~11
55d42d272ee30cd781e74a9c4ab152664c6417fc
v4.10-rc1~190^2~14^2~10
edaa78b4c050ec0a0fc7f436cdf6a73c91af64e0
v4.10-rc1~190^2~14^2~9
d8c303858582d4dcd90f13ebbe9db812a70d0948
v4.10-rc1~190^2~14^2~8
47cbd67e243a6bbb4133d719edd24ee6a315462d
v4.10-rc1~190^2~14^2~7
1b0978458300164046d12e1b7930c9de38057e1d
v4.10-rc1~190^2~14^2~6
6e82bdae472355fe0953e12eb29a36079e155ddb
v4.10-rc1~190^2~14^2~5
1f888acd92c8f88b0ab9640cef0794bc5424c668
v4.10-rc1~190^2~14^2~4
01dd25455b3588431d3f59c70e7b934a91d66121
v4.10-rc1~190^2~14^2~3
1fbd54b2e2356659f9f87920dc514792db6ff602
v4.10-rc1~190^2~14^2~2
2a81fa3bb5edb4a9dc9cb04cd591c99d41eb4f4c
v4.10-rc1~190^2~14^2~1
46b627a25f228adca952b8691e6aed32011cc3cf
v4.10-rc1~190^2~14^2
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1553178
Title:
perf: POWER8: Allow specifying Power PMU events by name rather than
raw codes
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
== Comment: #0 - Sukadev Bhattiprolu <s...@us.ibm.com> - 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://lkml.org/lkml/2015/10/26/624
== 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553178/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
