RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1757325 - perf top -p PID does not show anything
Summary: perf top -p PID does not show anything
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel
Version: 7.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Michael Petlan
QA Contact: Ziqian SUN (Zamir)
: 1757947 (view as bug list)
Depends On:
Blocks: 1710953 1793581
TreeView+ depends on / blocked
Reported: 2019-10-01 08:47 UTC by Michael Petlan
Modified: 2023-03-24 15:33 UTC (History)
14 users (show)

Fixed In Version: kernel-3.10.0-1101.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1793581 (view as bug list)
Last Closed: 2020-03-31 19:33:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 4467951 0 None None None 2019-10-25 13:59:58 UTC
Red Hat Product Errata RHSA-2020:1016 0 None None None 2020-03-31 19:34:38 UTC

Description Michael Petlan 2019-10-01 08:47:07 UTC
Description of problem:

Gregg Leventhal has found that `perf top -p $PID` does not work in RHEL-7.

Version-Release number of selected component (if applicable):
recent RHEL-7 perf, e.g. 3.10.0-1090.el7

How reproducible:

Steps to Reproduce:
yes > /dev/null &
perf top -p $!

Actual results:


Expected results:

perf top works

Comment 6 Jan Stancek 2019-10-07 07:11:50 UTC
Patch(es) committed on kernel-3.10.0-1101.el7

Comment 9 Michael Petlan 2019-10-08 12:05:09 UTC
*** Bug 1757947 has been marked as a duplicate of this bug. ***

Comment 10 Gregg Leventhal 2019-10-08 12:12:43 UTC
RHEL 7.8 is likely months away based on the cycle of previous releases.  Is there any change for a back-ported fix being released sooner than 7.8?  I'd like to get an estimated date so that I can find out if my employees are willing to wait for the upstream fix, or if I'll need to patch this in my environment.

Comment 12 Gregg Leventhal 2019-10-14 16:25:59 UTC
I just wanted to follow up and see if I can possibly get an ETA for 7.8 or the possibility of a back-port resolving this issue before then please.

Comment 14 Gregg Leventhal 2019-10-25 14:04:09 UTC
I ended up resolving this on my own for 7.7, so feel free to close (as far as I am concerned WRT to backporting to 7.7).

Comment 23 errata-xmlrpc 2020-03-31 19:33:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.