Bug 838746 - support multiple pids in set_pid_ftrace
support multiple pids in set_pid_ftrace
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: trace-cmd (Show other bugs)
Unspecified Unspecified
high Severity high
: rc
: 6.4
Assigned To: John Kacur
Guangze Bai
: FutureFeature
Depends On:
Blocks: 840683 769377
  Show dependency treegraph
Reported: 2012-07-09 21:21 EDT by Platform RFE
Modified: 2015-02-08 16:38 EST (History)
5 users (show)

See Also:
Fixed In Version: trace-cmd-1.0.5-9.el6
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 05:32:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0423 normal SHIPPED_LIVE trace-cmd bug fix and enhancement update 2013-02-20 15:49:27 EST

  None (edit)
Comment 5 Platform RFE 2012-07-09 21:21:41 EDT
** Original comment by snagar@redhat.com **

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?

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?


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

The noted above should work

7. Is there already an existing RFE upstream or in Red Hat bugzilla?


8. Does the customer have any specific timeline dependencies?


9. Is the sales team involved in this request and do they have any additional input?

10. List any affected packages

kernel, trace-cmd
Comment 14 errata-xmlrpc 2013-02-21 05:32:50 EST
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.