Help save net neutrality! Learn more.

oprofile-tests Log

Commit Date  
[ff956b] by Maynard Johnson Maynard Johnson

Add support for IBM POWER8 processor

Signed-off-by: Maynard Johnson <>

2014-02-12 19:34:13 Tree
[dc9651] by Carl E. Love Carl E. Love , pushed by Maynard Johnson Maynard Johnson

Testsuite, add tests for kallsyms, callgraph and debug info options

Add a test to verify that the kernel symbols were properly found in
/proc/kallsyms if the vmlinux file was not used.

Add test to verify /proc/kallsyms can be read.

Add test to verify the output format when the --debug-info and --symbols
options are used with opreport.

Add test to verify the --callgraph option at least produces some results.

The do_test procedure in oprofile-single_process-run.exp is moved to
lib/operf_util.exp and renamed do_single_process_test since it is now used
by tests in oprofile-operf-run.exp and oprofile-single_process-run.exp.

The do_test procedure in oprofile-operf-run.exp is also moved to
lib/operf_util.exp and renamed do_system-wide_test to keep the organization
of the test files similar.

Signed-off-by: Carl E. Love <>

2014-01-08 22:46:30 Tree
[967103] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

OProfile testsuite: Fix event name check in proc get_event_count

The recent patch to fix OProfile bug 253

"ocount does not display user specified unit mask, kerne and user values"

changed the output format when collecting in user or kernel mode only.
This change broke the testsuite function that extracted the count for a
given symbol because the expected symbol failed to match the symbol with
the user and kernel modes appended. This patch fixes the issue by spliting
the symbol from the output on colons and then checking the string before the

Signed-off-by: Carl Love <>

2013-12-11 15:11:47 Tree
[5855d1] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

oprofile-tests: Fix error message "Do not know how to handle version {1.0.0git}"

This patch fixes the message "Do not know how to handle version {1.0.0git}".
The current code requires that each new major version be added to the
case statement for versions greater then 0.5. Apparently, versions prior
to 0.5 were not supported by the testsuite for some now unkown reason. This
patch creates a specific case to handle the pre 0.5 versions, the 0.5 version
and all newer versions are handled by the default case. The case for the
pre 0.5 version of profile will simply print a message saying the version
is not supported. The case for version 0.5 is unchanged. The default
will handle all newer versions so this issue doesn't have to be continually
fixed with each major version change.

Signed-off-by: Carl Love <>

2013-10-08 21:18:46 Tree
[f8a53f] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

Add test for the ocount tool

The patch adds support for two additional testsuites for testing the ocount
tool. The first testsuite runs a series of tests on the ocount tool. The
tests include:

- each event generates non-zero counts
- counting for each event for an interval of n seconds, 2*n and 4*n scale as
- the sum of the counts for each event in user mode only, kernel mode
only match counting in user and kernel mode
- the output using the brief output format is verified

The above tests are run when the tool "oprofile" or "oprofile-ocount" are run.

The second testsuite includes the additional test:

- counting cycles for an interval of n seconds matches n*proc_frequency

This testsuite is only run when the tool "cycle-check-ocount" is specified.
The testsuite checks the event count against the reported CPU frequency which
may or may not be the actual operating CPU frequency. The reported frequency
and the actual frequency may differ if the CPU is running in the Intel "turbo"
mode or at a lower frequency for thermal management. The user may need to
manually verify any test failures based on the actual operating CPU frequency
not the reported CPU frequency.

Signed-off-by: Carl Love <>

2013-08-16 18:39:23 Tree
[f9d2e3] by Andi Kleen Andi Kleen , pushed by William Cohen William Cohen

Adjust the Intel Sandy Bridge event counts to allow use with Intel Haswell

The minimum event counts for Intel Haswell are just slightly higher
than the ones allowed by Intel Sandy Bridge and cause the tests to
fail without this adjustment in the event counts.

Signed-off-by: William Cohen <>

2013-07-25 21:38:23 Tree
[1cac98] by William Cohen William Cohen

Allow opcontrol tests to identify Intel Ivy Bridge and Sandy Bridge processors

For all the Intel processors that provide architected events reading
/dev/oprofile/cpu_type just returns i386/arch_perfmon. To get a more
exact list of events available the opcontrol tests need to examine
model number in /proc/cpuinfo. This patch adds recognition of Intel
Ivy Bridge and Intel Sandy Bridge processors.

Signed-off-by: William Cohen <>

2013-07-25 19:38:40 Tree
[82901d] by William Cohen William Cohen

Recognize the Intel Haswell processors for testing

Signed-off-by: William Cohen <>

2013-07-25 19:35:11 Tree
[778dbf] by William Cohen William Cohen

Factor out common code for processor name/events from opcontrol and operf tests

Want to avoid having two different places for the mapping of names to events.
This combines the code code for operf and opcontrol tests together.

Signed-off-by: William Cohen <>

2013-07-25 19:07:30 Tree
[36ab63] by William Cohen William Cohen

For operf tests purposes Intel Ivybridge and Intel Sandybridge are the same

The Intel Ivybridge is very similar to the Intel Sandybridge. The
testsuite was missing a definition for Ivybridge. Rather than making
yet another definition make the Intel Ivybridge use the Intel
Sandybridge definition.

Signed-off-by: William Cohen <>

2013-07-25 17:12:54 Tree
[656acf] by William Cohen William Cohen

Correct the specified processor type for ARM Cortex processors in the operf test

The ARM Cortex A5, Cortex A7, and Cortex A15 operf tests used an
undefined arm_cortex cpu type which has not been defined in the tests.
These architectures all include the common armv7 events and they can
safely use arm7 cpu type.

Signed-off-by: William Cohen <>

2013-07-25 13:55:58 Tree
[e53cd7] by Maynard Johnson Maynard Johnson

Adjust events for IBM POWER7 processor

The POWER7+ processor (which has the same events as POWER7)
has a much larger cache than POWER7. When running the
testsuite on POWER7+, the PM_BR_PRED_CCACHE event was not
being seen at all. I removed this event from the list of
events to monitor for since cache-related events are not
easy to deterministically predict for unknown processor
types. I also adjusted down the number of certain other
POWER7 events to help ensure the testing would "see" some
samples for those events.

Signed-off-by: Maynard Johnson <>

2013-03-05 17:36:31 Tree
[cbab12] by Maynard Johnson Maynard Johnson

Fix tcl workload symbol checking

Intermittently, the operf system-wide and operf single-process
tests fail after running the tcl workload (which executes a dd
command) and attempting to find the string "/bin/dd" in the
opreport output. The reason for this is two-fold:
- operf will profile child processes that a parent process will
fork/exec, but will terminate the profiling once the parent
process exits.
- The testsuite/workloads/tcl_src/workload.tcl script execs
the dd command as the last statement in the script and then

Considering the two facts stated above, it's clear that profiling
of the dd command may or may not occur, depending on timing.
Once the parent tcl process exits, operf will detect the parent
exiting and will shutdown profiling. Some samples may have been
collected for the dd command before this shutdown occurs, but maybe

To avoid this timing issue, this patch simply changes the symbol
we check for in the tcl profile output from "/bin/dd" to "libtcl".

Signed-off-by: Maynard Johnson <>

2012-10-18 18:47:35 Tree
[e2a4ff] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

OProfile testsuite, add single process profiling functionality

This patch adds another test to the suite of tests. The test runs each of
the workloads with operf in single process mode. The test verifies that
samples were collected for each run. The test checks to make sure the
symbols were found for the first event group, just as is done in the
oprofile-operf test. The testsuite can be run as root or as a regular user.

Signed-off-by: Carl Love <>

2012-10-18 12:43:35 Tree
[485655] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

OProfile testsuite, Add symbol checking functionality

This patch adds additional testing and workload capability. The
patch adds the capability to easily add a new workload specification
and a list of symbols that should be present in the OProfile report.
The testsuite runs each of the specified workloads with each of the
event lists currently specified. The output from opreport is
checked to verify the workload symbols are found.

Signed-off-by: Carl Love <>

2012-10-09 14:24:07 Tree
[533c95] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

Oprofile testsuite, fix proc op_daemon_delete_any_samples, it doesn't work correctly

The op_daemon_delete_any_samples procedure is not correctly deleting
samples. This patch replaces the body of the procedure with the
"opcontrol --reset" call to remove the existing samples. The patch
also moves the function to lib/op_util.exp so it can be called by
the operf testsuite as well. A call to op_daemon_delete_any_samples was
added to the operf test main routine to make sure any opcontrol samples are
deleted so opreport will not pickup any samples from a previous opcontrol

Signed-off-by: Carl Love <>

2012-10-05 19:43:25 Tree
[63fb4a] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

OProfile testsuite, fix perf kill command

The operf user tool expects to get a kill -SIGINT signal. However
the SIGINT signal can not be sent from a script, it must come from
the command line. Hence the pkill -P command was used to kill the
parent and children processes. A bug was found in that the pkill
command kills operf without letting it completely finish the data
processing and exit cleanly. This issue actually was found when
testing a patch that is currently under development to check for
specific symbols. The kill -INT signal can be sent from the script
and is properly caught by operf. When operf catches the INT signal
it shuts down cleanly rather then exiting immediatly. This patch
fixes the current kill command to make sure operf exits cleanly.

Signed-off-by: Carl Love <>

2012-09-28 14:13:30 Tree
[6112f9] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

OProfile testsuite, change operf version check fail to warning

This patch changes the operf version test failure to a warning instead
of a failure. Also, the user message that is printed is changed to
be more explicit that the user tool operf is not supported rather then
using the term "system" which could be interpreted as meaning the
kernel. The patch specifically addresses systems with a perf enabled
kernel but an older (OProfile 0.9.7 or older) user space tool that
does not have support for the new operf user interface.

Signed-off-by: Carl Love <>

2012-09-27 18:32:27 Tree
[e21569] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

OProfile testsuite, add operf support to the testsuite

This patch adds support for the basic testing of the new
operf user interface. It leverages the existing event
tables for the various processors. OProfile has its own
kernel support for the names of the processors. This
information is only available when the OProfile kernel
module is loaded. The operf support gets the CPU name from
the ophelp command instead.

The patch also fixes an error in the existing opcontol testsuite.
Specifically, the test for the string "opcontrol error:" will always
fail because the output from the command does not include the word
"opcontrol". Removed "opcontrol" from the test string.

Added commands to the opcontrol testsuite to make sure the
daemonrc file is removed. This is necessary to ensure there are no
extraneous settings, for example filter settings, that will cause errors.

Trailing blanks on five lines in the existing files were removed.

The testsuit for testing OProfile using the opcontrol interface
has been renamed to oprofile-opcontrol. The new testsuite to
test OProfile using operf is called oprofile-operf. To run both
testsuites, use the testsuite oprofile. Specifically the commands
to run the testsuites are:

runtest --tool oprofile-opcontrol // test opcontrol interface

runtest --tool oprofile-operf // test operf interface

runtest --tool oprofile // test both interfaces

Signed-off-by: Carl Love <>

2012-09-26 18:19:39 Tree
[57f9f5] by William Cohen William Cohen

Add recognition for additional armv7 cortex processors

2012-08-09 21:30:26 Tree
[9cd24c] by William Cohen William Cohen

Update the armv7 event names

A July 2, 2012 patch to oprofile changed some of the event names for
armv7 processors. This patch update events used in the tests to those

2012-08-09 21:19:27 Tree
[acf470] by Carl Love Carl Love , pushed by Maynard Johnson Maynard Johnson

OProfile testsuite, fix white spaces

This patch cleans up trailing white spaces, spaces before tabs. In the
lib/op_events.exp file, the tables of events were cleaned up to use
tabs and spaces consistently, fix the consistency on the location of the
line contiuation charcter. Additionally, the patch makes sure that the
files all end with a blank line consisting of a single space.

Signed-off-by: Carl Love <>
Signed-off-by: Maynard Johnson <>

2012-07-20 18:39:50 Tree
[a72027] by William Cohen William Cohen

Add tests to verify the Intel Sandy Bridge extra cmask is working.

2011-08-01 22:03:43 Tree
[841f65] by William Cohen William Cohen

Revert "Add tests to check that the Intel Sandybridge "extra" umask support works."

This reverts commit 35e3e11f1e58c709fd82850533b0f38c107fe7b8.

2011-08-01 21:46:41 Tree
[71fbb3] by William Cohen William Cohen

Add tests to check that the Intel Sandybridge "extra" umask support works.

2011-08-01 21:40:54 Tree
Older >