Tue Dec 5 20:10:50 2017 -0800  William Cohen <wcohen@redhat.com>

	* src/libpfm4/lib/events/power9_events.h,

	  src/libpfm4/tests/validate_power.c: Update libpfm4 Current with

	  commit 206dea666e7c259c7ca53b16f934660344293475  Ensure unique

	  names for IBM Power 9 events  Older versions of PAPI use the event

	  name to look up the libpfm event number when doing the enumeration

	  of the available events.  If there were multiple events with the

	  same name in libpfm, the earliest one would be selected.  This

	  selection would cause the enumeration of events in

	  papi_native_avail to get stuck looping on the first duplicated

	  named event in a pmu.  In the case of IBM Power 9 the enumeration

	  would get stuck on PM_CO0_BUSY. Gave each event a unique name to

	  avoid this unfortunate behavior.

2017-11-16  Will Schmidt <will_schmidt@vnet.ibm.com>

	* src/papi_events.csv: revised papi_derived patch.  [PATCH, papi]

	  Updated derived entries for power9.  This is a re-implementation of

	  the patch that Will Cohen posted earlier, which uses the (newly

	  defined) PM_LD_MISS_ALT entry instead of the PM_LD_MISS_FIN .

	  Thanks, -Will

2017-12-05  Heike Jagode (jagode@icl.utk.edu) <jagode@saturn.icl.utk.edu>

	* release_procedure.txt: Updated notes for release procedure.

2017-12-05  Vince Weaver <vincent.weaver@maine.edu>

	* src/extras.c: extras.c: add string.h include to make the ffsll

	  warning go away

2017-12-04  Heike Jagode (jagode@icl.utk.edu) <jagode@saturn.icl.utk.edu>

	* src/configure, src/configure.in: Fixed configure bug:  Once ffsll

	  support is detected, set HAVE_FFSLL to 1 in config.h.  Tested

	  without configure flag --with-ffsll, with --with-ffsll=yes, --with-

	  ffsll=no.

2017-12-04  Vince Weaver <vincent.weaver@maine.edu>

	* src/ctests/Makefile.recipies, src/ctests/locks_pthreads.c: ctests:

	  locks_pthreads: adjust run count again  linear slowdown makes

	  things run really quickly. This patch scales it down by the square

	  root of the number of cores which is maybe a better compromise.

	* src/ctests/locks_pthreads.c: ctests: locks_pthreads, minor cleanups

2017-11-20  William Cohen <wcohen@redhat.com>

	* src/ctests/locks_pthreads.c: Keep locks_pthreads test's amount of

	  work reasonable on many core machines  The runtime of

	  locks_pthreads test scaled by the number of processors on the

	  machine because of the serialized increment operation in the test.

	  As more machines are available with 100+ processors the runtime of

	  locks_pthreads is becoming execessive.  Revised the test to specify

	  the approximate total number of iterations and split the work the

	  threads.

Fri Dec 4 11:31:46 2015 -0500  sangamesh <sragate@vols.utk.edu>

	* src/extras.c, src/papi.h: Revert change that added ffsll to papi.h

	  This reverts commit 2f1ec33a9e585df1b6343a0ea735f79974c080df.

	  commit 2f1ec33a9e585df1b6343a0ea735f79974c080df  changed #if

	  (!defined(HAVE_FFSLL) || defined(__bgp__)) int ffsll( long long lli

	  ); #endif --- to --- extern int ffsll( long long lli  in extras.c

	  to avoid warning when --with-ffsll is used as config option

Thu Apr 20 11:31:38 2017 -0400  Stephen Wood <swood@icl.utk.edu>

	* src/extras.c, src/papi.h: revert part of patch that added extra

	  attributes to ffsll  This manually reverts part of:  commit

	  9e199a8aee48f5a2c62d891f0b2c1701b496a9ca  cast pointers

	  appropriately to avoid warnings and errors

Sun Dec 3 09:42:44 2017 -0800  Will Schmidt <will_schmidt@vnet.ibm.com>

	* src/libpfm4/lib/events/power9_events.h,

	  src/libpfm4/tests/validate_power.c: Updated libpfm4  Current with:

	  ---------------- commit ed3f51c4690685675cf2766edb90acbc0c1cdb67

	  (HEAD -> master, origin/master, origin/HEAD)  Add alternate event

	  numbers for power9.  I had previously missed adding the _ALT

	  entries, which allow some events to be specified on different

	  counters. This patch fills those in.  This patch also adds a few

	  validation tests for the ALT events.  ----------------

2017-11-28  Heike Jagode (jagode@icl.utk.edu) <jagode@saturn.icl.utk.edu>

	* src/utils/papi_avail.c, src/utils/papi_native_avail.c: Fixed

	  utility option inconsistencies between papi_avail and

	  papi_native_avail. There are more inconsistencies with other PAPI

	  utilities, which will be addressed eventually.

2017-11-28  Heike Jagode <jagode@icl.utk.edu>

	* README.md: README.md edited online with Bitbucket

	* README.md: README.md edited online with Bitbucket

	* README.md: README.md edited online with Bitbucket

	* README.md: README.md edited online with Bitbucket

2017-11-27  Heike Jagode <jagode@icl.utk.edu>

	* src/components/powercap/linux-powercap.c: More clean-ups and

	  checking of return values.

Mon Nov 13 23:15:53 2017 -0800  Thomas Richter <tmricht@linux.vnet.ibm.com>

	* src/libpfm4/lib/pfmlib_common.c: Update libpfm4” > /tmp/commit-

	  libpfm4-header.txt echo “Current with commit

	  f5331b7cbc96d9f9441df6a54a6f3b6e0fab3fb9  better fix for

	  pfmlib_getl()  The following commit:  commit

	  9c69edf67f6899d9c6870e9cb54dcd0990974f81  better param check in

	  pfmlib_getl()  Fixed paramter checking of pfmlib_getl() but missed

	  one condition on the buffer argument. It is char **buffer.

	  Therefore we need to check if *buffer is not NULL before we can

	  check *len.

2017-11-19  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/cuda/linux-cuda.c: CUDA component: Bug fix for

	  releasing and resetting event list  When an event addition failed

	  because the event (or metric) requires multiple-runs the eventlist

	  and event-context structure was not being cleaned up properly.

	  This fixes the event cleanup process.

2017-11-17  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/powercap/tests/powercap_basic.c,

	  src/components/powercap/tests/powercap_limit.c: Powercap component:

	  Updated tests to handle no-event-counters (num_cntrs==0) and skip

	  some compiler warnings (argv, argc unused)

2017-11-16  William Cohen <wcohen@redhat.com>

	* src/components/lmsensors/linux-lmsensors.c: Make more of lmsensors

	  component internal state hidden  There are a number of functions

	  pointers stored in variable that are only used within the lmsensors

	  component.  Making those static ensures they are not visible

	  outside the lmsensors component.

	* src/components/lmsensors/linux-lmsensors.c: Make internal

	  cached_counts variable static  Want to make as little information

	  about the internals of the PAPI lmsensors component visible to the

	  outside.  Thus, making cached_counts variable static.

2017-11-15  William Cohen <wcohen@redhat.com>

	* src/components/lmsensors/linux-lmsensors.c: Avoid statically

	  limiting the number of lmsensor events allowed  Some high-end

	  server machines provide more events than the 512 entries limit

	  imposed by the LM_SENSORS_MAX_COUNTERS define in the lmsensor

	  component (observed 577 entries on one machine).  When this limit

	  was exceeded the lmsensor component would write beyond the array

	  bounds causing ctests/all_native_events to crash.  Modified the

	  lmsensor code to dynamically allocate the required space for all

	  the available lmsensor entries on the machine. This allows

	  ctests/all_native_events to run to completion.

	* src/components/appio/appio.c, src/components/coretemp/linux-

	  coretemp.c, src/components/example/example.c,

	  src/components/infiniband/linux-infiniband.c, src/components/lustre

	  /linux-lustre.c, src/components/rapl/linux-rapl.c: Use correct

	  argument order for calloc function calls  Some calls to calloc in

	  PAPI have the order of the arguments reversed. According to the

	  calloc man page the number of elements is the first argument and

	  the size of each element is the second argument.  Due to alignment

	  constraints the second argument might be rounded up.  Thus, it is

	  best not to not to swap the arguments to calloc.

2017-11-15  Philip Vaccaro <pvaccaro@vols.utk.edu>

	* src/components/powercap/linux-powercap.c,

	  src/components/powercap/tests/powercap_basic.c: Updates and changes

	  to the powercap component to address a few areas.. Various things

	  were changed but mainly things were simplified and made more

	  streamlined.  Main focus was on simpifying managing the sytem

	  files.

Mon Nov 13 23:15:53 2017 -0800  Thomas Richter <tmricht@linux.vnet.ibm.com>

	* src/libpfm4/docs/man3/pfm_get_event_encoding.3,

	  src/libpfm4/docs/man3/pfm_get_os_event_encoding.3,

	  src/libpfm4/lib/events/amd64_events_fam11h.h,

	  src/libpfm4/lib/events/amd64_events_fam12h.h,

	  src/libpfm4/lib/pfmlib_common.c, src/libpfm4/lib/pfmlib_priv.h,

	  src/libpfm4/tests/validate_x86.c: Update libpfm4  Current with

	  commit 9c69edf67f6899d9c6870e9cb54dcd0990974f81  better param check

	  in pfmlib_getl()  This patch ensures tha len >= 2 because we do: m

	  = l - 2;  Reviewed-by: Hendrik Brueckner

	  <brueckner@linux.vnet.ibm.com>

2017-11-13  Vince Weaver <vincent.weaver@maine.edu>

	* src/components/perf_event/pe_libpfm4_events.c: pe_libpfm4_events:

	  properly notice if trying to add invalid umask  this passes the

	  broken-event test case and all of the unit tests, but it would be

	  good to test this on codes that do a lot of native event tests.

	  the pe_libpfm4_events code *really* needs a once-over, it is

	  currently a confusing mess.

	* src/components/perf_event/tests/Makefile,

	  src/components/perf_event/tests/broken_events.c,

	  src/components/perf_event/tests/event_name_lib.c,

	  src/components/perf_event/tests/event_name_lib.h: perf_event/tsts:

	  add broken event name test  we were wrongly accepting event names

	  with invalid umasks

2017-11-13  Philip Mucci <mucci@icl.utk.edu>

	* src/utils/print_header.c: Removed extraneous colon in VM vendor

	  output

2017-11-10  Vince Weaver <vincent.weaver@maine.edu>

	* src/validation_tests/papi_l1_dcm.c,

	  src/validation_tests/papi_l2_dcm.c,

	  src/validation_tests/papi_l2_dcr.c,

	  src/validation_tests/papi_l2_dcw.c: validation_tests: fix compiler

	  warnings on arm32  On Raspberry Pi we were getting warnings where

	  we were printing sizeof() valus with %ld.  Convert to %zu instead.

2017-11-09  Vince Weaver <vincent.weaver@maine.edu>

	* src/validation_tests/papi_l2_dca.c: validation_tests: papi_l2_dca

	  fix crash on ARM32  On raspberry pi it's not possible to detect L2

	  cache size so the test was dividing by zero.

	* src/linux-common.c: linux-common: remove warning on not finding mhz

	  in cpuinfo  This was added recently and is not needed. Most ARM32

	  devices don't have MHz in the cpuinfo file and it's not really a

	  bug.

	* src/components/perf_event/perf_event.c: perf_event: disable the old

	  pre-Linux-2.6.34 workarounds by default  There were a number of

	  bugs in perf_event that PAPI had to work around, but most of these

	  were fixed by 2.6.34  In order to hit these bugs you would need to

	  be running a kernel from before 2010 which wouldn't support any

	  recent hardware.  Unfortunately these bugs are hard to test for.

	  We were enabling things based on kernel versions, but this caught

	  vendors (such as Redhat) shipping 2.6.32 kernels that had

	  backported fixes.  This fix just #ifdefs things out, if no one

	  complains then we can fully remove the code.

	* src/components/perf_event/perf_event.c: perf_event: decrement the

	  available counter count if NMI_WATCHDOG is stealing one

	* src/components/perf_event/perf_event.c: perf_event: move the

	  paranoid handling code to its own function

	* src/components/perf_event/perf_event.c: perf_event: centralize

	  fast_counter_read flag  just use the component version of the flag,

	  rather than having a shadow global version.

2017-11-09  William Cohen <wcohen@redhat.com>

	* src/linux-memory.c: Make the fallback generic_get_memory_info

	  function more robust  On the aarch64 processor linux 4.11.0 kernels

	  /sys/devices/system/cpu/cpu0/cache is available, but the index[0-9]

	  subdirectories are not fully populated with information about cache

	  and line size, associativity, or number of sets.  These missing

	  files would cause the generic_get_memory_info function to attempt

	  to read data using a NULL file descriptor causing the program to

	  crash.  Added checks to see if every fopen was and fscan was

	  successful and just say there is no cache if there is any failure.

2017-11-09  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/cuda/linux-cuda.c,

	  src/components/cuda/tests/Makefile,

	  src/components/nvml/tests/Makefile, src/configure,

	  src/configure.in: Enable icc and nvcc to work together in cuda and

	  nvml components.  For nvcc to work with Intel icc to compile cuda

	  and nvml components and tests , it needs to use nvcc -ccbin=<$CC-

	  compilerbin> . The compiler name in CC also needs to be clean, so

	  CC=<compilerbin> and any other flags are pushed to CFLAGS (changed

	  in src/configure.in script).

	* src/ctests/mpifirst.c: Minor correction to mpifirst.c test

2017-11-09  Vince Weaver <vincent.weaver@maine.edu>

	* src/utils/print_header.c: utils: print fast_counter_read (rdpmc)

	  status in the utils header

2017-11-08  William Cohen <wcohen@redhat.com>

	* src/validation_tests/cache_helper.c: Ensure access to array within

	  bounds  Coverity reported the following issues.  Need the test to

	  be "type>=MAX_CACHE" rather than "type>MAX_CACHE".  Error: OVERRUN

	  (CWE-119): papi-5.5.2/src/validation_tests/cache_helper.c:85:

	  cond_at_most: Checking "type > 4" implies that "type" may be up to

	  4 on the false branch.

	  papi-5.5.2/src/validation_tests/cache_helper.c:90: overrun-local:

	  Overrunning array "cache_info" of 4 24-byte elements at element

	  index 4 (byte offset 96) using index "type" (which evaluates to 4).

	  Error: OVERRUN (CWE-119):

	  papi-5.5.2/src/validation_tests/cache_helper.c:101: cond_at_most:

	  Checking "type > 4" implies that "type" may be up to 4 on the false

	  branch. papi-5.5.2/src/validation_tests/cache_helper.c:106:

	  overrun-local: Overrunning array "cache_info" of 4 24-byte elements

	  at element index 4 (byte offset 96) using index "type" (which

	  evaluates to 4).  Error: OVERRUN (CWE-119):

	  papi-5.5.2/src/validation_tests/cache_helper.c:117: cond_at_most:

	  Checking "type > 4" implies that "type" may be up to 4 on the false

	  branch. papi-5.5.2/src/validation_tests/cache_helper.c:122:

	  overrun-local: Overrunning array "cache_info" of 4 24-byte elements

	  at element index 4 (byte offset 96) using index "type" (which

	  evaluates to 4).

	* src/ctests/overflow_pthreads.c: Eliminate coverity overflow warning

	  about expression

	* src/components/perf_event_uncore/tests/perf_event_uncore_lib.c:

	  Remove dead code from perf_event_uncore_lib.c

2017-11-09  Vince Weaver <vincent.weaver@maine.edu>

	* src/components/perf_event/perf_event.c: perf_event: don't

	  initialize globals statically  from the mucci-5.5.2 tree

2017-11-08  phil@minimalmetrics.com <phil@minimalmetrics.com>

	* src/linux-common.c: linux-common: clean up the /proc/cpuinfo

	  parsing code  From the mucci-cleanup branch

	* src/components/perf_event/perf_event.c,

	  .../perf_event_uncore/perf_event_uncore.c,

	  src/papi_libpfm4_events.c, src/papi_libpfm4_events.h: perf_event:

	  clean up _papi_libpfm4_shutdown()  From the mucci-cleanup branch

	* src/utils/print_header.c: utils: clean up the cpuinfo header  From

	  the mucci-cleanup branch

	* src/papi_internal.c, src/papi_internal.h: papi_internal: add

	  PAPI_WARN() function  From the mucci-cleanup branch

	* src/components/perf_event/pe_libpfm4_events.c: perf_event: clean up

	  pe_libpfm4_events  From the mucci-cleanup branch  --

2017-11-08  Vince Weaver <vincent.weaver@maine.edu>

	* src/utils/papi_avail.c: utils/papi_avail: update the manpage info

	  based on changes by Phil Mucci

	* .../perf_event/tests/perf_event_system_wide.c: perf_event tests:

	  perf_event_system_wide: don't fail if permissions restrict system-

	  wide events  right now we just skip if we get EPERM, we should also

	  maybe check the perf_event_paranoid setting and print a more

	  meaningful report

	* src/ctests/locks_pthreads.c: ctests/locks_pthreads: avoid printing

	  values when in quiet mode

2017-08-31  phil@minimalmetrics.com <phil@minimalmetrics.com>

	* src/Makefile.inc: Better symlink creation for shared library in

	  make phase

2017-08-28  phil@minimalmetrics.com <phil@minimalmetrics.com>

	* doc/Makefile, src/.gitignore, src/Makefile.inc,

	  src/components/.gitignore, src/components/Makefile_comp_tests,

	  src/ctests/.gitignore, src/ctests/Makefile.recipies,

	  src/ftests/.gitignore, src/ftests/Makefile.recipies,

	  src/testlib/.gitignore, src/utils/.gitignore, src/utils/Makefile,

	  src/validation_tests/.gitignore,

	  src/validation_tests/Makefile.recipies: Full cleanup, including

	  removal of .gitignore files that prevented us from realizing we

	  were really cleaning/clobbering properly

	* src/validation_tests/.gitignore: .gitignore Makefile.target

	* src/papi.c: Remove PAPI_VERB_ECONT setting by default from

	  initialization path. This prints all kinds of needless errors on

	  virtual platforms.

	* src/x86_cpuid_info.c: Remove leftover printf

2017-08-21  phil@minimalmetrics.com <phil@minimalmetrics.com>

	* src/ctests/locks_pthreads.c: Test now performs a fixed number of

	  iterations, and reports lock/unlock timings per thread.

	* src/components/perf_event/perf_event.c: Added more descriptive

	  error message to exclude_guest check

	* src/papi_internal.c: Removed leading newline and trailing . from

	  error messages

	* src/papi_preset.c: Updated message for derived event failures

2017-11-07  Vince Weaver <vincent.weaver@maine.edu>

	* src/Makefile.inc, src/ctests/Makefile,

	  src/ctests/Makefile.target.in, src/ftests/Makefile,

	  src/ftests/Makefile.target.in, src/testlib/Makefile.target.in,

	  src/utils/Makefile.target.in, src/validation_tests/Makefile,

	  src/validation_tests/Makefile.target.in: tests: make sure DESTDIR

	  and DATADIR are passed in when doing an install

	* src/ctests/Makefile, src/ctests/Makefile.target.in,

	  src/ftests/Makefile, src/ftests/Makefile.target.in,

	  src/utils/Makefile, src/utils/Makefile.target.in,

	  src/validation_tests/Makefile,

	  src/validation_tests/Makefile.target.in:

	  ctests/ftests/utils/validation_tests: get shared library linking

	  working again  This should let the various tests and utils be

	  linked as shared libraries again.

	* src/validation_tests/Makefile: validation_tests: add an

	  installation target  this makes the validation tests have an

	  install target, like the ctests and ftests

	* src/ctests/Makefile, src/ftests/Makefile: ctests/ftests: fix

	  "install" target  at some point DATADIR was renamed datadir and the

	  install targets were not updated.

2017-11-07  Asim YarKhan <yarkhan@icl.utk.edu>

	* bitbucket-pipelines.yml: Bitbucket pipeline testing: Inspired by

	  Phil Mucci's branch; copied the functionalty tests run in that

	  branch.

	* src/components/lmsensors/linux-lmsensors.c: lmsensors component:

	  Changed event names to use lm_sensors (only once) instead of

	  LM_SENSORS (twice) to be consistent with other events

2017-11-02  William Cohen <wcohen@redhat.com>

	* src/components/appio/tests/iozone/gnu3d.dem: gnu3d.dem should not

	  be executed by the test framework  This file is a gnuplot file and

	  should not be executed as part of the tests. Removing the

	  executable perms will signal to the testing framework that it

	  shouldn't be executed.

	* src/components/appio/tests/iozone/Gnuplot.txt: Gnuplot.txt should

	  not be executed by the test framework  This file is a readme file

	  and should not be executed as part of the tests. Removing the

	  executable perms will signal to the testing framework that it

	  shouldn't be executed.

	* .../appio/tests/iozone/iozone_visualizer.pl,

	  src/components/appio/tests/iozone/report.pl: Fix perl scripts so

	  they run on Linux machines  The DOS style newlines were preventing

	  Linux from selecting the appropriate interpreter for these scripts

	  and causing these tests to fail.

2017-11-07  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/lmsensors/configure: lmsensors component: Regenerate

	  the configure file for the component

2017-11-02  William Cohen <wcohen@redhat.com>

	* src/components/lmsensors/Makefile.lmsensors.in,

	  src/components/lmsensors/configure.in, src/components/lmsensors

	  /linux-lmsensors.c: Make the lmsensors dynamically load the needed

	  shared library  When attempting to build the current git repo of

	  papi the build of the files in the utils subdirectory failed

	  because the lmsensors libraries were not being linked in.  Rather

	  than forcing the papi to link in the lmsensor library during the

	  build the lmsensors component has been modified to dynamically load

	  the needed libraries and enable the lmsensors events when

	  available.  This allows machines missing the lmsensor libraries

	  installed to still use papi.

2017-11-06  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/cuda/linux-cuda.c: CUDA component: On architectures

	  without CUDA Metrics (e.g. Tesla C2050), skip metric registration

	  rather than returning errors

2017-11-06  Vince Weaver <vince@deater.net>

	* src/validation_tests/papi_l2_dca.c,

	  src/validation_tests/papi_l2_dcm.c,

	  src/validation_tests/papi_l2_dcr.c,

	  src/validation_tests/papi_l2_dcw.c: validation_tests: make the

	  papi_l2 tests fail with warnings  On Haswell/Broadwell and newer

	  these tests fail for unknown reasons.  This isn't new behavior,

	  it's just that the tests are new.  It's unlikely we will have time

	  to completely sort this out before the upcoming release, so change

	  the FAIL to WARN so testers won't be unnecessarily alarmed.

2017-11-05  Vince Weaver <vincent.weaver@maine.edu>

	* src/components/perf_event/perf_event.c, src/configure,

	  src/configure.in: perf_event: enable rdpmc support by default  It

	  can still be disabled at configure time with --enable-perfevent-

	  rdpmc=no  This speeds up PAPI_read() by at least a factor of 5x

	  (see the ESPT'17 workshop presentation)  It is only enabled on

	  Linux 4.13 and newer due to bugs in previous versions.

2017-11-03  Vince Weaver <vincent.weaver@maine.edu>

	* src/ctests/sdsc-mpx.c: ctests: sdsc: fix issue where the error

	  message is not printed correctly

2017-11-01  Heike Jagode <jagode@icl.utk.edu>

	* src/components/powercap/linux-powercap.c: Intermediate check-in:

	  Fixed a whole bunch of careless file handling (missing closing of

	  open files, missing setting of open/close flag, etc). Still more

	  rigorous checks needed.

Mon Oct 30 17:16:32 2017 -0700  Stephane Eranian <eranian@gmail.com>

	* src/libpfm4/lib/events/intel_skl_events.h: Update

	  libpfm4\n\nCurrent with\n commit

	  21405fb3c247a0d16861483daf0696cf4fa0cc43  update SW_PREFETCH event

	  for Intel Skylake  Event was renamed SW_PREFETCH_ACCESS, but we

	  keep SW_PREFETCH as an alias.  Added PREFETCHW umask.  Enabled

	  suport for both Skylake client and server as per official event

	  table from 10/27/2017. See download.01.org/perfmon/

2017-10-30  Vince Weaver <vincent.weaver@maine.edu>

	* src/validation_tests/Makefile.recipies,

	  src/validation_tests/cycles.c,

	  src/validation_tests/cycles_validation.c: validation_tests: add

	  cycles_validation test  this is the old zero test, which does a

	  number of cycles tests  It should be extended to add more.

2017-10-30  Vince Weaver <vince@deater.net>

	* src/ctests/attach2.c, src/ctests/attach3.c, src/ctests/calibrate.c,

	  src/ctests/child_overflow.c, src/ctests/code2name.c,

	  src/ctests/earprofile.c, src/ctests/exec_overflow.c,

	  src/ctests/fork_overflow.c, src/ctests/hwinfo.c, src/ctests/mendes-

	  alt.c, src/ctests/prof_utils.c, src/ctests/prof_utils.h,

	  src/ctests/profile.c, src/ctests/remove_events.c,

	  src/ctests/shlib.c, src/ctests/system_child_overflow.c,

	  src/ctests/system_overflow.c, src/ctests/zero_named.c,

	  src/testlib/papi_test.h, src/testlib/test_utils.c: papi: c++11

	  fixes: fix various ctests that c++ complains on  mostly just const

	  warnings, some K+R function declarations, and possibly an actual

	  char/char* bug.

	* src/papi.c, src/papi.h: papi: c++11 conversion:

	  PAPI_get_component_index()

	* src/papi.c, src/papi.h: papi: c++11 conversion: convert

	  PAPI_perror()

	* src/aix.c, src/components/appio/appio.c,

	  src/components/bgpm/CNKunit/linux-CNKunit.c,

	  src/components/bgpm/IOunit/linux-IOunit.c,

	  src/components/bgpm/L2unit/linux-L2unit.c,

	  src/components/bgpm/NWunit/linux-NWunit.c, src/components/emon

	  /linux-emon.c, src/components/net/linux-net.c,

	  src/components/perf_event/pe_libpfm4_events.c,

	  src/components/perf_event/pe_libpfm4_events.h,

	  src/components/perf_event/perf_event.c,

	  .../perf_event_uncore/perf_event_uncore.c,

	  src/components/perfmon_ia64/perfmon-ia64.c, src/freebsd.c, src

	  /linux-bgq.c, src/papi.c, src/papi.h, src/papi_internal.c,

	  src/papi_internal.h, src/papi_libpfm3_events.c,

	  src/papi_libpfm_events.h, src/papi_vector.c, src/papi_vector.h:

	  papi: start converting papi.h to be C++11 clean  Most of the issues

	  have to do with string to char * conversion.  This first patch

	  converts PAPI_event_name_to_code()  The issue was first reported by

	  Brian Van Straalen

	* src/validation_tests/papi_l2_dca.c: validation_tests/papi_l2_dca:

	  update some comments

	* src/ctests/zero.c, src/validation_tests/cycles.c: ctests/zero: make

	  test pass on recent intel machines  The test was failing due to the

	  PAPI_get_real_cycles() validation on recent Intel chips.  This is

	  probably something that should be tested in a separate test and not

	  in zero which is supposed to be a bare-bones are-things-working

	  test.

2017-10-27  Philip Vaccaro <pvaccaro@vols.utk.edu>

	* src/components/powercap/README: updated powercap README to be more

	  concise. includes more details on interacting with energy counters

	  and power limits.

2017-10-27  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/cuda/linux-cuda.c, src/components/nvml/linux-nvml.c:

	  CUDA/NVML components: Handled segfault which can occur when

	  dlclosing libcudart from both components by adding an additional

	  flag to dlopen

2017-10-24  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/cuda/linux-cuda.c,

	  src/components/cuda/tests/simpleMultiGPU.cu: CUDA component: Clean

	  up fulltest by moving some output from stdout to SUBDBG, removed

	  some commented out lines

	* src/components/nvml/linux-nvml.c: nvml component: To support V100

	  (Volta) updated to get nvmlDevice handle ordered by index rather

	  than pci busid.

2017-10-23  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/cuda/linux-cuda.c: CUDA component: Minor fix to

	  remove some unneeded stdout which shows up during fulltest

2017-10-20  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/cuda/linux-cuda.c,

	  src/components/cuda/tests/Makefile,

	  src/components/cuda/tests/simpleMultiGPU.cu: CUDA component test

	  update: Remove some debug output.  Do not build cupti_only test

	  binary.

Thu Oct 19 11:23:44 2017 -0700  Stephane Eranian <eranian@gmail.com>

	* src/libpfm4/examples/showevtinfo.c,

	  src/libpfm4/lib/events/intel_skl_events.h: Update

	  libpfm4\n\nCurrent with\n commit

	  2e98642dd331b15382256caa380834d01b63bef8  Fix Intel Skylake

	  EXE_ACTIVITY.1_PORTS_UTIL event  Was missing a umask name.

2017-10-17  Vince Weaver <vincent.weaver@maine.edu>

	* src/ctests/version.c: ctests: version, add INCREMENT field  at the

	  request of Steve Kaufmann

	* src/ctests/Makefile.recipies, src/ctests/version.c: ctests: re-

	  enable version test  not sure why it was disabled

	* src/ctests/Makefile.recipies: ctests: alphabetize SERIAL tests in

	  Makefile.recipes

2017-10-13  Philip Vaccaro <pvaccaro@vols.utk.edu>

	* src/components/powercap/tests/Makefile,

	  src/components/powercap/tests/powercap_limit.c: added simple limit

	  test for the powercap component.

2017-10-09  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/nvml/linux-nvml.c: Big Fix NVML component: Fix

	  problem with names when there are multiple identical GPUs  If

	  multiple identical GPUs were available, the names were not mapped

	  correctly.  Fixed event names to be

	  "nvml:::Tesla_K40c:device_0:myevent" rather than

	  "nvml:::Tesla_K40c_0:myevent".

Fri Sep 29 00:25:09 2017 -0700  Stephane Eranian <eranian@gmail.com>

	* src/libpfm4/include/perfmon/perf_event.h,

	  src/libpfm4/lib/events/intel_skl_events.h,

	  src/libpfm4/lib/events/s390x_cpumf_events.h,

	  src/libpfm4/lib/pfmlib_s390x_cpumf.c,

	  src/libpfm4/perf_examples/Makefile,

	  src/libpfm4/perf_examples/branch_smpl.c,

	  src/libpfm4/perf_examples/perf_util.c: Update libpfm4\n\nCurrent

	  with\n commit d1e7c96df60a00a371fdaa3b635ad4a38cee4c2f  add new

	  branch_smpl.c perf_events example  This patch adds a new example to

	  demo how to sample and parse the PERF_SAMPLE_BRANCH_STACK record

	  format of perf_events. It will dump branches taken from the sampled

	  command.

2017-10-05  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/nvml/README, src/components/nvml/linux-nvml.c,

	  src/components/nvml/linux-nvml.h,

	  src/components/nvml/tests/HelloWorld.cu,

	  src/components/nvml/tests/Makefile,

	  .../nvml/tests/nvml_power_limiting_test.cu: Update NVML component:

	  Support for power limiting using NVML  PAPI has added support for

	  power limiting using NVML (on supported devices from the Kepler

	  family or later).  The executable needs to have root permissions to

	  change the power limits on the device.  We have added new events to

	  the NVML component to support power management limits.  The

	  nvml:::DEVICE:power_management_limit can be written (as well as

	  read), but requires higher permissions (root level).  The limit is

	  constrainted between a min and a max value, which can be read.

	  When the component is unloaded, the power_management_limit should

	  be reset to the initial value.

	  nvml:::DEVICE:power_management_limit

	  nvml:::DEVICE:power_management_limit_constraint_min

	  nvml:::DEVICE:power_management_limit_constraint_max  A new test

	  (nvml/tests/nvml_power_limiting_test.cu)/ was written to check if

	  the writing functionality works (with the proper hardware and

	  permissions).

2017-10-04  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/nvml/linux-nvml.c, src/components/nvml/linux-nvml.h,

	  src/components/nvml/tests/HelloWorld.cu: Style consistency and

	  refactoring via astyle command.  No changes to the actual code were

	  made here.

2017-10-04  Vince Weaver <vincent.weaver@maine.edu>

	* src/components/rapl/linux-rapl.c: rapl: add support for some Intel

	  Atom models Goldmont / Gemini_Lake / Denverton

	* src/components/rapl/linux-rapl.c: rapl: fix skylake SoC measurement

	  support

	* src/components/rapl/linux-rapl.c: rapl: add support for skylake SoC

	  energy measurements

	* src/components/rapl/linux-rapl.c: rapl: add Skylake-X / Kabylake

	  support

	* src/components/rapl/linux-rapl.c: rapl: centralize the "different

	  DRAM units" code

	* src/components/rapl/linux-rapl.c: rapl: merge like processors

	* src/components/rapl/linux-rapl.c: rapl: convert chip detection to a

	  switch statement

	* src/components/rapl/linux-rapl.c: rapl: update the whitespace a bit

2017-09-12  Heike Jagode (jagode@icl.utk.edu) <jagode@saturn.icl.utk.edu>

	* .../infiniband_umad/linux-infiniband_umad.c, .../infiniband_umad

	  /linux-infiniband_umad.h: Fixed papi_vector for infiniband_umad

	  component.  The array of function pointers that the component

	  defines must use the naming convention papi_vector_t _x_vector

	  where x is the name of the component directory.  In this case, the

	  name of the component directory is infiniband_umad and not

	  infiniband.  This change has not been tested yet due to OFED lib

	  issues on our local machines. There may be more changes required in

	  order to get the infiniband_umad component to work properly.

2017-09-11  Hanumanth <fhanuman@vols.utk.edu>

	* man/man1/papi_avail.1, man/man1/papi_native_avail.1,

	  src/utils/papi_avail.c, src/utils/papi_native_avail.c: Updating man

	  and help pages for papi_avail and papi_native_avail

2017-09-07  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/cuda/tests/nvlink_bandwidth.cu,

	  .../cuda/tests/nvlink_bandwidth_cupti_only.cu: Update to CUDA

	  component to support NVLink.  The CUDA component has been cleaned

	  up and updated to support NVLink. NVLink metrics can not be

	  measured properly in KERNEL event collection mode, so the CUPTI

	  EventCollectionMode is transparently set to

	  CUPTI_EVENT_COLLECTION_MODE_CONTINUOUS when a NVLink metric is

	  being measured in an eventset.  For all other events and metrics,

	  the CUDA component uses the KERNEL event collection mode.  A bug in

	  the earlier version was that repeated calls to add CUDA events were

	  failing because some structures were not cleaned up.  This should

	  now be fixed.  A new nvlink test was added to the CUDA component

	  tests.

2017-08-31  Phil Mucci <phil@minimalmetrics.com>

	* man/man1/papi_avail.1, man/man1/papi_clockres.1,

	  man/man1/papi_command_line.1, man/man1/papi_component_avail.1,

	  man/man1/papi_cost.1, man/man1/papi_decode.1,

	  man/man1/papi_error_codes.1, man/man1/papi_event_chooser.1,

	  man/man1/papi_hybrid_native_avail.1, man/man1/papi_mem_info.1,

	  man/man1/papi_multiplex_cost.1, man/man1/papi_native_avail.1,

	  man/man1/papi_version.1, man/man1/papi_xml_event_info.1,

	  man/man3/PAPI_cleanup_eventset.3, man/man3/PAPI_destroy_eventset.3:

	  Updating options for papi_avail/native_avail as well as all

	  references to old mailing list

2017-08-31  Asim YarKhan <yarkhan@icl.utk.edu>

	* src/components/nvml/linux-nvml.c,

	  src/components/nvml/tests/HelloWorld.cu,

	  src/components/nvml/tests/Makefile: Minor updates to NVML component

	  to enable it to compile and run without complaints

2017-08-30  Vince Weaver <vincent.weaver@maine.edu>

	* src/validation_tests/papi_br_prc.c,

	  src/validation_tests/papi_br_tkn.c: validation: update papi_br_prc

	  and papi_br_tkn for amd fam15h  amd fam15h doesn't have a

	  conditional branch event so the measures have to be against total.

	  for now print warning, maybe we should let it go w/o a warning.

	* src/papi_events.csv: papi_events: add PAPI_BR_PRC event to amd

	  fam15h

	* src/papi_events.csv: papi_events: update PAPI_BR_PRC and

	  PAPI_BR_TKN on sandybridge/ivybridge  They were using TOTAL

	  branches for the derived branch events rather than CONDITIONAL like

	  the other modern x86 processors were using.

	* src/validation_tests/papi_br_tkn.c: validation_tests: papi_br_tkn:

	  update to only count conditional branches

	* src/validation_tests/papi_br_prc.c: validation_tests: papi_br_prc:

	  make sure it is comparing conditional branches  was doing total

	  branches, which made the test fail on skylake

Mon Aug 21 23:55:46 2017 -0700  Stephane Eranian <eranian@gmail.com>

	* src/libpfm4/lib/pfmlib_intel_x86.c: Update libpfm4\n\nCurrent

	  with\n commit a290dead7c1f351f8269a265c0d4a5f38a60ba29  fix usage

	  of is_model_event() for Intel X86  This patch fixes a couple of

	  problems introduced by commit: 77a5ac9d43b1 add model field to

	  intel_x86_entry_t  The code in pfm_intel_x86_get_event_first() was

	  incorrect. It was calling is_model_event() before checking if the

	  index was within bounds. It should have been the opposite. Same

	  issue in pfm_intel_x86_get_next_event(). This could cause SEGFAULT

	  as report by Phil Mucci.  The patch also fixes the return value of

	  pfm_intel_x86_get_event_first(). It was not calculated correctly.

	  Reported-by: Phil Mucci <mucci@icl.utk.edu>

2017-08-20  Vince Weaver <vincent.weaver@maine.edu>

	* src/ctests/Makefile.recipies, src/ctests/failed_events.c: ctests:

	  add failed_events test  it tries to create invalid events to make

	  sure the event parser properly handles invalid events.

2017-08-19  Vince Weaver <vincent.weaver@maine.edu>

	* src/components/perf_event_uncore/tests/Makefile,

	  .../perf_event_uncore/tests/perf_event_uncore.c,

	  .../tests/perf_event_uncore_attach.c: perf_event_uncore: tests:

	  update perf_event_uncore to use :cpu=0  This is the more common way

	  of specifying uncore events. Rename the old test that uses

	  PAPI_set_opt() to perf_event_uncore_attach

	* .../tests/perf_event_uncore_cbox.c,

	  .../tests/perf_event_uncore_lib.c,

	  .../tests/perf_event_uncore_lib.h: perf_event_uncore: tests: update

	  uncore events for recent processors

	* src/ctests/zero_pthreads.c: ctests: zero_pthreads: remove

	  extraneous printf when in quiet mode

	* .../tests/perf_event_uncore_lib.c: perf_event_uncore: event list,

	  add recent processors  libpfm4 still doesn't support regular

	  Haswell, Broadwell, or Skylake machines

	* .../perf_event_uncore/tests/perf_event_uncore.c,

	  .../tests/perf_event_uncore_cbox.c,

	  .../tests/perf_event_uncore_multiple.c: perf_event_uncore: tests:

	  print a message indicating the problem on skip  also some

	  whitespace cleanups

	* src/components/perf_event/tests/event_name_lib.c: perf_event:

	  tests: update event_name_lib for recent Intel processors

	* src/components/perf_event/tests/event_name_lib.c: perf_event:

	  tests: event_name_lib, clean up whitespace

	* .../perf_event/tests/perf_event_offcore_response.c: perf_event:

	  tests: update perf_event_offcore_response test  print an indicator

	  of why we are skipping the test also some gratuitous whitespace

	  cleanups

	* src/ctests/zero_shmem.c: ctests: zero_shmem: document the code a

	  little better

	* src/ctests/zero_smp.c: ctests: zero_smp: make it actually do

	  something on Linux  Linux can use the pthread code just like AIX

	  although we don't validate the results, so this test could be

	  another candidate for not being necessary anymore.

	* src/ctests/zero_shmem.c: ctests: zero_shmem: minor cleanups  we

	  pretty much always skip this test.  Is it needed anymore? What was

	  it testing in the first place?  The code it calls (start_pes() )

	  doesn't seem to exist anymore

	* src/ctests/zero_omp.c, src/ctests/zero_pthreads.c: ctests: zero_omp

	  and zero_pthread were skipping due to a typo  when updating the

	  code I had left a stray ! before PAPI_query_event()

2017-08-19  Vince Weaver <vince@deater.net>

	* src/papi_events.csv: papi_events: the skylake fixes broke hsw/bdw

	  this skylake-x change is way more trouble than it was worth.

2017-08-19  Vince Weaver <vincent.weaver@maine.edu>

	* src/papi_events.csv: papi_events: on skylake the SNP_FWD umask was

	  renamed to SNP_HIT_WITH_FWD  This broke presets on skylake,

	  skylake-x

	* src/components/perf_event/pe_libpfm4_events.c: perf_event: fix

	  uninitialized descr issue reported by valgrind  I don't think this

	  is the skylake-x bug though

2017-08-18  Vince Weaver <vincent.weaver@maine.edu>

	* src/components/perf_event/pe_libpfm4_events.c: perf_event: clean up

	  some whitespace in pe_libpfm4_events.c

	* src/linux-memory.c: linux-memory: various errors when compiling

	  with debug enabled  the new proc memory code had some mistakes in

	  the debug messages that only appeared when compiled with --with-

	  debug  Reported-by: Steve Kaufmann <sbk@cray.com>

2017-08-17  Vince Weaver <vincent.weaver@maine.edu>

	* src/papi_events.csv: papi_events: missed one of the skx event

	  locations

2017-08-16  Vince Weaver <vincent.weaver@maine.edu>

	* src/papi_events.csv: papi_events: enable Skylake X support

Sun Aug 6 00:22:52 2017 -0700  Stephane Eranian <eranian@gmail.com>

	* src/libpfm4/include/perfmon/pfmlib.h,

	  src/libpfm4/lib/events/intel_skl_events.h,

	  src/libpfm4/lib/pfmlib_common.c,

	  src/libpfm4/lib/pfmlib_intel_skl.c,

	  src/libpfm4/lib/pfmlib_intel_snbep_unc.c,

	  src/libpfm4/lib/pfmlib_intel_x86.c,

	  src/libpfm4/lib/pfmlib_intel_x86_priv.h,

	  src/libpfm4/lib/pfmlib_priv.h, src/libpfm4/tests/validate_x86.c:

	  Update libpfm4\n\nCurrent with\n commit

	  efd16920194999fdf1146e9dab3f7435608a9479  add support for Intel

	  Skylake X  This patch adds support for Intel Skylake X core PMU

	  events. Based on

	  download.01.org/perfmon/SKX/skylakex_core_v25.json.  New PMU is

	  called skx.

2017-08-07  Vince Weaver <vincent.weaver@maine.edu>

	* src/papi_events.csv: papi_events: add initial AMD fam17h support

	  not tested on actual hardware yet

	* src/papi_events.csv: papi_events: fix the amd_fam16h PMU name  The

	  way libpfm4 reports fam16h was modified a bit from my initial

	  patches.  fam16h seems to be working now.

Thu Jul 27 23:30:20 2017 -0700  Stephane Eranian <eranian@gmail.com>

	* src/libpfm4/README, src/libpfm4/docs/Makefile,

	  src/libpfm4/docs/man3/libpfm_amd64_fam16h.3,

	  src/libpfm4/docs/man3/libpfm_amd64_fam17h.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_cbo.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_ha.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_imc.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_irp.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_pcu.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_qpi.3,

	  .../docs/man3/libpfm_intel_bdx_unc_r2pcie.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_r3qpi.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_sbo.3,

	  src/libpfm4/docs/man3/libpfm_intel_bdx_unc_ubo.3,

	  src/libpfm4/examples/showevtinfo.c,

	  src/libpfm4/include/perfmon/pfmlib.h, src/libpfm4/lib/Makefile,