|
Packit |
577717 |
2013-05-21
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 602d8dbc man/man1/papi_avail.1 man/man1/papi_clockres.1
|
|
Packit |
577717 |
man/man1/papi_command_line.1...: Rebuild man pages for a 5.1.1 release.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 93d9be34 doc/Doxyfile-common papi.spec src/Makefile.in...: Bump version
|
|
Packit |
577717 |
number for a 5.1.1 release.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-04-15
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 8e47838d src/components/cuda/linux-cuda.c: When creating two event sets -
|
|
Packit |
577717 |
one for the CUDA and one for the CPU component - the order of event set
|
|
Packit |
577717 |
creation appears crucial. When the CPU event set has been created before the
|
|
Packit |
577717 |
CUDA event set then PAPI_start() for the CUDA event set works fine. However,
|
|
Packit |
577717 |
if the CUDA event set has been created before the CPU event set, then
|
|
Packit |
577717 |
PAPI_start(CUDA_event_set) forces the CUDA control state to be updated one
|
|
Packit |
577717 |
more time, even if the CUDA event set has not been modified. The CUDA control
|
|
Packit |
577717 |
state function did not properly handle this case and hence cause PAPI_start()
|
|
Packit |
577717 |
to fail. This has been fixed.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-05-13
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* c93dfa68 src/perf_events.c: perf_event component: update error returns
|
|
Packit |
577717 |
This passes more error return values back to PAPI. Before this change a lot
|
|
Packit |
577717 |
of places were hardcoded to PAPI_EPERM even if sys_perf_event_open() was
|
|
Packit |
577717 |
reporting a different error.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-05-08
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* d1db58e8 src/configure src/configure.in: Force the use of pthread_mutexes
|
|
Packit |
577717 |
on ARM This lets the system libraries worry about the best way to define
|
|
Packit |
577717 |
mutexes, rather than trying to hand-code in assembly around all of the
|
|
Packit |
577717 |
various issues there are with atomic instructions in the ARM architecture.
|
|
Packit |
577717 |
It might make sense to enable this for *all* Linux architectures, but for now
|
|
Packit |
577717 |
just do it for ARM.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 29662e3e src/linux-lock.h: Commit 59d3d7584b2925bd05b4b5d0f4fe89666eb8494a
|
|
Packit |
577717 |
removed the definition of mb(). mb() was defined as rmb(). This just
|
|
Packit |
577717 |
corrects it back. (Note from VMW -- this fixes some things, but ARM still
|
|
Packit |
577717 |
won't build on a Cortex A9 pandaboard due to the use of the "swp"
|
|
Packit |
577717 |
instruction. Proper fix is probably to enforce posix-mutexes on ARM)
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-04-22
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* ff29fd12 src/run_tests.sh: The test for determining whether to run valgrind
|
|
Packit |
577717 |
was backwards. Correcting that allow the run_test.sh script to stay the same
|
|
Packit |
577717 |
and one just needs to define "VALGRIND=yes" (or any non-null string) to make
|
|
Packit |
577717 |
run_test.sh use valgrind. --- src/run_tests.sh | 6 ++---- 1 file changed, 2
|
|
Packit |
577717 |
insertions(+), 4 deletions(-) diff --git a/src/run_tests.sh
|
|
Packit |
577717 |
b/src/run_tests.sh index d1ce205..9337ff2 100755 --- a/src/run_tests.sh +++
|
|
Packit |
577717 |
b/src/run_tests.sh @@ -19,10 +19,8 @@ else export TESTS_QUIET fi -if [
|
|
Packit |
577717 |
"x$VALGRIND" = "x" ]; then -# Uncomment the following line to run tests using
|
|
Packit |
577717 |
Valgrind -# VALGRIND="valgrind --leak-check=full"; - VALGRIND=""; +if [
|
|
Packit |
577717 |
"x$VALGRIND" != "x" ]; then + VALGRIND="valgrind --leak-check=full"; fi
|
|
Packit |
577717 |
#CTESTS=`find ctests -maxdepth 1 -perm -u+x -type f`; --
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-28
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 1e8101f6 src/run_tests.sh: run_tests.sh: further refine component test find
|
|
Packit |
577717 |
Exclude *.cu when looking for component tests.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-25
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 0b600bc5 src/run_tests.sh: run_tests.sh: File mode changes. run_tests.sh
|
|
Packit |
577717 |
is now expected to run from the install location in addition to src. The
|
|
Packit |
577717 |
script tried to remove execute from *.[c|h], now it just excludes *.[c|h]
|
|
Packit |
577717 |
from the find commands.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-18
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 06f9c43b src/perfctr-x86.c: perfctr: don't read in event table multiple
|
|
Packit |
577717 |
times papi_libpfm3_events.c now reads in the predefined events, we don't
|
|
Packit |
577717 |
also need to do this in perfctr setup_x86_presets()
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 48d7330c src/perfctr.c: Fix segfault in perfctr.c The preset lookup uses
|
|
Packit |
577717 |
the cidx index, but in perfctr.c we weren't passing a cidx value (it was
|
|
Packit |
577717 |
being left off). The old perfctr code plays games with defining extern
|
|
Packit |
577717 |
functions so the compiler wasn't giving us a warning.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-14
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* eda94e50 src/components/bgpm/L2unit/linux-L2unit.c src/linux-bgq.c: If a
|
|
Packit |
577717 |
counter is not set to overflow (threshold==0; happens when PAPI_shutdown is
|
|
Packit |
577717 |
called) then we do not want to rebuild the BGPM event set, even if the event
|
|
Packit |
577717 |
set has been used previously and hence "applied or attached". Usually if an
|
|
Packit |
577717 |
event set has been applied or attached prior to setting overflow, the BGPM
|
|
Packit |
577717 |
event set needs to be deleted and recreated (which implies malloc() from
|
|
Packit |
577717 |
within BGPM). Not so, though, if threshold is 0 which is the case when
|
|
Packit |
577717 |
PAPI_shutdown is called. Note, this only applies to Punit and L2unit, not
|
|
Packit |
577717 |
IOunit since an IOunit event set in not applied or attached.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-13
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 46f6123a src/components/bgpm/IOunit/linux-IOunit.c
|
|
Packit |
577717 |
src/components/bgpm/IOunit/linux-IOunit.h
|
|
Packit |
577717 |
src/components/bgpm/L2unit/linux-L2unit.c...: Overflow issue on BG/Q
|
|
Packit |
577717 |
resolved. Overflow with multiple components worked; overflow with multiple
|
|
Packit |
577717 |
components and multiple events did not work as supposed to.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-07
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 6a0813f8 src/linux-common.c src/linux-memory.c: Fix the build on
|
|
Packit |
577717 |
Linux-SPARC I dug out an old SPARC machine and fixed the PAPI build on it.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 51fe7e53 src/perf_events.c: More comprehensive sys_perf_open to PAPI error
|
|
Packit |
577717 |
mappings This tries to cover more of the errors returned by sys_perf_open
|
|
Packit |
577717 |
and map them to better results. EINVAL is a problem because it can mean
|
|
Packit |
577717 |
Conflict as well as Event not found and many other things, so it's unclear
|
|
Packit |
577717 |
what to do with it.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 1479a67f src/perf_events.c src/sys_perf_event_open.c: Return proper error
|
|
Packit |
577717 |
codes for sys_perf_event_open For some reason on x86 and x86_64 we were
|
|
Packit |
577717 |
trying to set errno manually and thus over-writing the proper errno value,
|
|
Packit |
577717 |
causing all errors to look like PAPI_EPERM This removes that code, as well
|
|
Packit |
577717 |
as adds code to report ENOENT as PAPI_ENOEVENT. With this change, on IVY
|
|
Packit |
577717 |
this happens which looks more correct. ./utils/papi_command_line
|
|
Packit |
577717 |
perf::L1-ICACHE-PREFETCHES Failed adding: perf::L1-ICACHE-PREFETCHES because:
|
|
Packit |
577717 |
Event does not exist command_line.c PASSED
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-06
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 7a3e75e8 src/papi_libpfm4_events.c src/papi_user_events.c: Coverity fixes:
|
|
Packit |
577717 |
Coverity pointed out that there was a case where load_user_eent_table() could
|
|
Packit |
577717 |
leak memory. The change in the location of the papi_free(foo) ensures that
|
|
Packit |
577717 |
the allocated memory is freed. Coverity pointed out one path through the
|
|
Packit |
577717 |
code in _papi_libpfm4_ntv_code_to_descr() that did not free up memory
|
|
Packit |
577717 |
allocated in the function. Added a free on the path in free up that memory.
|
|
Packit |
577717 |
Thanks Will Cohen.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-04
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* b19bd1a2 src/components/rapl/linux-rapl.c: Remove a stray debug statement.
|
|
Packit |
577717 |
Thanks to Harald Servat for catching this.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-03-01
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 6e5be510 src/utils/command_line.c: Wrestled some horribly convoluted
|
|
Packit |
577717 |
indexing into shape. The -u and -x options now print as expected (I think).
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-01-31
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 02bd70ad src/components/nvml/linux-nvml.c: linux-nvml.c: Fix type warning.
|
|
Packit |
577717 |
CUDA and NVML have an signed vs unsigned thing going on in their returned
|
|
Packit |
577717 |
device counts, cast away the warning.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-01-23
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* a5bed384 src/linux-memory.c src/linux-timer.c: ia64 fixes. Thanks to Tony
|
|
Packit |
577717 |
Jones <tonyj@suse.de> for patches.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-01-16
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 021db23a src/components/nvml/linux-nvml.c: nvml component: cleanup a memory
|
|
Packit |
577717 |
leak We did not free a buffer at shutdown time.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-05-17
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* b25fc417 src/perf_events.c: perf_event: allow running with
|
|
Packit |
577717 |
perf_event_paranoid is 2 perf_event_paranoid set to 2 means allow user
|
|
Packit |
577717 |
monitoring only (no kernel domain). The code before this mistakenly disabled
|
|
Packit |
577717 |
all events in this case. Also set the allowed domains to exclude
|
|
Packit |
577717 |
PAPI_DOM_KERNEL.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-05-16
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 12768bec src/papi_events.csv: papi_events.csv Revert a little mishap in
|
|
Packit |
577717 |
adding ivbep support Somehow the contents of papi_hl.c ended up in the
|
|
Packit |
577717 |
events file.
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* 5e97ad7f src/papi_events.csv: Add identifier for ivb_ep
|
|
Packit |
577717 |
|
|
Packit |
577717 |
2013-01-29
|
|
Packit |
577717 |
|
|
Packit |
577717 |
* e201b8eb src/papi.c: General doxygen cleanup: remove all "No known bugs"
|
|
Packit |
577717 |
messages; correct and cleanup examples for PAPI_code_to_name and
|
|
Packit |
577717 |
PAPI_name_to_code
|