[ oprofile-Bugs-3412988 ] Problems with daemonrc cached event list

[SourceForge.net <no...@so...>]

Bugs item #3412988, was opened at 2011-09-22 10:44
Message generated for change (Comment added) made by maynardj
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116191&aid=3412988&group_id=16191

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: William Cohen (wcohen)
Assigned to: Nobody/Anonymous (nobody)
Summary: Problems with daemonrc cached event list

Initial Comment:
opcontrol caches the oprofile events in /root/.oprofile/daemonrc.  If someone explicitly sets the events like this:

opcontrol --deinit
echo 0 > /proc/sys/kernel/nmi_watchdog
opcontrol --start --event=CPU_CLK_UNHALTED:1000000:0:1:1
opcontrol --shutdown

There will be an entry in /root/.oprofile/daemonrc for the event:

CHOSEN_EVENTS_0=CPU_CLK_UNHALTED:1000000:0:1:1

This presents a problem if one tries to use the timer mode:

opcontrol --deinit
modprobe oprofile timer=1
opcontrol --start

Get the following error message:

You cannot specify any performance counter events
because OProfile is in timer mode.

Get rid of the daemonrc file and oprofile starts up:

# rm /root/.oprofile/daemonrc 
# opcontrol --start --no-vmlinux
Using 2.6+ OProfile kernel interface.
Using log file /var/lib/oprofile/samples/oprofiled.log
Daemon started.
Profiler running.


OProfile should be better about the caches list of events in daemonrc.


----------------------------------------------------------------------

>Comment By: Maynard Johnson (maynardj)
Date: 2012-07-06 08:30

Message:
Marking as Fixed (see my 2011-12-06 comment).

----------------------------------------------------------------------

Comment By: Maynard Johnson (maynardj)
Date: 2011-12-06 13:41

Message:
Will, please take a look at the s390 patch that was posted today.  Check
out the change made to opcontrol, context line # 421 (pasted below for
convenience).  That change seems to fix the problem described in this bug
report.

+
+	# Ignore configured events when running in timer mode.
+	if test "$IS_TIMER" = 1; then
+		NR_CHOSEN=0
+	fi




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116191&aid=3412988&group_id=16191