Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
** Original comment by snagar **
Description of problem:
1. Proposed title of this feature request
Support multiple pids in set_pid_ftrace
2. Who is the customer behind the request?
<Confidential>
3. What is the nature and description of the request?
Jiri Olsa submitted a patch back in '09 that makes it possible to filter ftrace data based on multiple pid's rather than only one. I believe this patch is now upstream. This doesn't seem to be in RHEL6 yet so could you backport it?
https://lkml.org/lkml/2009/9/16/83
trace-cmd would also need to be adjusted accordingly and support multiple -P options:
trace-cmd record -p function -P 30192,16429
or, alternatively:
trace-cmd record -p function -P 30192 -P 16429
4. Why does the customer need this? (List the business requirements here)
It enhances the functionality of ftrace which they make extensive use of
5. How would the customer like to achieve this? (List the functional
requirements here)
Noted above
6. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.
The noted above should work
7. Is there already an existing RFE upstream or in Red Hat bugzilla?
No
8. Does the customer have any specific timeline dependencies?
No
9. Is the sales team involved in this request and do they have any additional input?
No
10. List any affected packages
kernel, trace-cmd
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.
http://rhn.redhat.com/errata/RHBA-2013-0423.html