Bug 84168 – oprofile driver should accept hex values

Bug 84168 - oprofile driver should accept hex values

Summary:	oprofile driver should accept hex values

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Arjan van de Ven
QA Contact:	Brian Brock
Docs Contact:

URL:	http://www.uwsg.indiana.edu/hypermail...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-02-12 18:30 EST by William Cohen
Modified:	2005-10-31 17:00 EST (History)
CC List:	0 users

See Also:
Fixed In Version:	/kernel-2.4.22-1.2115.nptl.src.rpm
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-01-21 16:06:10 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description William Cohen 2003-02-12 18:30:40 EST

Description of problem:

Files in /dev/oprofile/ should be able to accept hex value, e.g. 0xf stated in
the oprofile documentation. 


Version-Release number of selected component (if applicable):

kernel-2.4.20-2.41, oprofile-0.4-40

How reproducible:

On p4 machine

Steps to Reproduce:
1. opcontrol --setup --ctr3-event=INSTR_RETIRED --ctr3-count=240000
--ctr3-unit-mask=0xf --vmlinux=/boot/vmlinux-2.4.20-2.41smp
2. opcontrol --start
3.
    
Actual results:

oprofiled: ctr3: 0x00: invalid unit mask for cpu P4 / Xeon
Couldn't start oprofiled.

Expected results:

oprofile starts without problem.

Additional info:

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