Hide Forgot
Created attachment 479734 [details] Patch to the spec file Being able to analyze the results of Ftrace in a GUI environment is extremely valuable. I've attached a patch to the trace-cmd spec file that: * Builds kernelshark in a separate subpackage * Cleans up various packaging bugs Please consider these for inclusion. Also, I notice that trace-cmd is currently not packaged for Fedora in any form. I plan on submitting this package to Fedora unless you want to. Note that on another bug, bug 676146, I have a review request going on to include just the GUI parts in EPEL, however, it would be easier just to take this patch into RHEL than have me maintain something that necessarily must track what you do (though I can do that).
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
2. What is the nature and description of the request? include kernelshark in RHEL 3. Why does the customer need this? (List the business requirements here) These tools are vast improvements over what we have today in terms of tracing. They offer an lttng like gui, where you can pick apart stuff from a graph and more easily dig down in the code and transform data when it comes to stuff like call graphs. 4. How would the customer like to achieve this? (List the functional requirements here) kernelshark rpms 5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. yum install kernelshark starts installing 6. Is there already an existing RFE upstream or in Red Hat bugzilla? No 7. How quickly does this need resolved? (desired target release) minor 8. Does this request meet the RHEL Inclusion criteria (please review) yes 9. List the affected packages kernelshark 10. Would the customer be able to assist in testing this functionality if implemented? Not specified.
Thank you for submitting this feature request for inclusion in Red Hat Enterprise Linux. Your request will be considered in a future release of Red Hat Enterprise Linux.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux.
Thank you for filing this feature request. At this point, we will not be able to incorporate this request into RHEL6. Steve