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 463369 - [LTC 6.0 FEAT] 200977:PAPI runtime and development
Summary: [LTC 6.0 FEAT] 200977:PAPI runtime and development
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: distribution
Version: 6.0
Hardware: ppc64
OS: All
high
high
Target Milestone: alpha
: 6.0
Assignee: Steve Best
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On: 463365
Blocks: 356741 532993 554559
TreeView+ depends on / blocked
 
Reported: 2008-09-23 03:10 UTC by IBM Bug Proxy
Modified: 2010-07-12 12:42 UTC (History)
6 users (show)

Fixed In Version: papi-3.7.2-4.el6
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-12 12:42:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description IBM Bug Proxy 2008-09-23 03:10:45 UTC
=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-16 18:30 EDT
1. Feature Overview:
Feature Id:	[200977]
a. Name of Feature:	PAPI runtime and development
b. Feature Description
The Performance API (PAPI) project specifies a standard application programming interface (API) for
accessing hardware performance counters available on most modern microprocessors.  This feature is
dependent on feature 200974.

Additional Comments:	papi is at http://icl.cs.utk.edu/papi/index.html

2. Feature Details:
Sponsor:	PPC
Architectures:
ppc64

Arch Specificity: Both
Delivery Mechanism: Direct from community
Category:	Toolchain
Request Type:	Package - New
d. Upstream Acceptance:	Accepted
Sponsor Priority	2
f. Severity: Medium
IBM Confidential:	no
Code Contribution:	IBM code
g. Component Version Target:	papi 3.6 (or later)

3. Business Case
The PAPI tool is used to collect performance data in large clustered environments.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Michael Hohnbaum, hbaum.com, 503-578-5486

Technical contact(s):
Steven Munroe, sjmunroe.com
Maynard Johnson, mpjohn.com

IBM Manager:
Alexander Johnson, acjohnso.com

Comment 1 Bill Nottingham 2008-10-02 16:26:53 UTC
Marking as dependent on perfmon2.

Comment 2 IBM Bug Proxy 2009-08-31 22:31:02 UTC
------- Comment From mpjohn.com 2009-08-31 18:28 EDT-------
This PAPI feature depends on a kernel interface to the performance monitoring hardware.  Such an interface is the topic of another IBM feature request for RHEL 6 -- IBM bug # 48182, RH # 463365.  As stated there, the original plan was to include perfmon2 in RHEL 6 since perfmon2 seemed to be on track for probable acceptance into the kernel at that time.  But in late 2008, an alternative kernel interface to PM hardware was proposed ("Performance Counters for Linux", aka "PCL").  The implementation for this new interface has now been accepted into the kernel.  A new "PCL" substrate was required to enable PAPI to function on top of PCL versus perfmon2.  We have contributed such a substrate to the PAPI project, and it was accepted on July 13, 2009.

As of this date, the PCL support in PAPI is not yet available in an official release.  Assuming the PCL feature is accepted (RH # 463365), then a PAPI CVS snapshot from some date after 07/13/2009 should be used for building the PAPI package for RHEL 6.

Thank you.

Comment 5 John Jarvis 2009-11-12 19:52:15 UTC
The package will be available in beta 1.

Comment 6 IBM Bug Proxy 2009-11-30 03:30:26 UTC
------- Comment From mpjohn.com 2009-11-29 22:28 EDT-------
Changing status to ACCEPTED based on previous comment from Red Hat.

Comment 7 John Jarvis 2009-11-30 16:29:13 UTC
IBM is signed up to test and provide feedback.

Comment 9 Kevin W Monroe 2009-12-01 22:10:48 UTC
Reassigning to Steve Best, the new IBM on-site partner.

Comment 10 William Cohen 2009-12-17 15:09:31 UTC
The performance event support is in the 2.6.31 and newer kernel. PAPI-3.7 and newer versions of PAPI have support for the Linux Performance Event Support. PAPI-3.7.2 has been built for RHEL-6.

Comment 12 IBM Bug Proxy 2010-04-27 20:51:18 UTC
------- Comment From cjashfor.com 2010-04-27 16:43 EDT-------
Successfully ran the ctests from PAPI-3.7.2 on a Power7 machine (alien4.ltc.austin.ibm.com) running RHEL 6 beta with the PAPI rpm installed.

Comment 14 Chris Ward 2010-07-12 12:42:29 UTC
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. One or more confirmation reports have already been received confirming this. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.


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