Bug 1757947

Summary:	perf top "-p" functionality is broken in perf-3.10.0-1062.1.1.el7.x86_64
Product:	Red Hat Enterprise Linux 7	Reporter:	Brandon Clark <brclark>
Component:	kernel	Assignee:	Michael Petlan <mpetlan>
kernel sub component:	Perf	QA Contact:	Kernel General QE <kernel-general-qe>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	acme, alanm, amike, brclark, casantos, gleventhal, jolsa, jwright, knweiss, mbliss, mkolbas, mpetlan
Version:	7.7
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-08 12:05:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brandon Clark 2019-10-02 19:33:14 UTC

Description of problem:
perf top -p $PID doesn't work as reported in https://bugzilla.kernel.org/show_bug.cgi?id=203203

Version-Release number of selected component (if applicable):
perf-3.10.0-1062.1.1.el7.x86_64
Red Hat Enterprise Linux 7

How reproducible:
Consistently reproducible.

Steps to Reproduce (From fresh install):
1.Ensure RHEL 7.7 is installed, 
2.Ensure above version of perf is installed.
3. run 'perf top -p <pid>' substituting <pid> with process pid of choice.

Actual results:
"Samples: 0  of event 'cpu-clock'" displayed in perf output

Expected results:
Samples to be displayed in perf output

Comment 4 Gregg Leventhal 2019-10-04 18:36:30 UTC

It seems like some important info from the original ticket is missing, which is that I believe I already know the 2 commits which resolve this issue:


1e6db2ee86e6a4399fc0ae5689e55e0fd1c43caf
1e5b0cf8672e622257df024074e6e09bfbcb7750

I simply want to know how soon this will be fixed, so I know whether I need to build and maintain a patched RPM myself, or if I can just wait for RHEL to offer the fix.

Comment 5 Michael Petlan 2019-10-08 12:05:09 UTC

Hello Gregg. This issue has been already fixed in RHEL-7 and the bits are under testing right now. The fixed package will be released within RHEL-7.8.
Closing this bug as a dupe of bz1757325 which I filed based on your e-mail report and which tracks the issue already. I've also made the mentioned bug public.

*** This bug has been marked as a duplicate of bug 1757325 ***