dolysis
/
benchmark
mirror of https://github.com/google/benchmark.git
3
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
benchmark/cmake/Modules/FindPFM.cmake

29 lines
959 B
CMake
Raw Permalink Normal View History

Support optional, user-directed collection of performance counters (#1114) * Support optional, user-directed collection of performance counters The patch allows an engineer wishing to drill into the root causes of a regression, for example. Currently, only single threaded runs are supported. The feature is a build-time opt in, and then a runtime opt in. The engineer may run the benchmark executable, passing a list of performance counter names (using libpfm's naming scheme) at the command line. The counter values will then be collected and reported back as UserCounters. This is different from #240 in that it is a benchmark user opt-in, and the counter collection is transparent to the benchmark. Currently, this is only supported on platforms where libpfm is supported. libpfm: http://perfmon2.sourceforge.net/ * 'Use' values param in Snapshot when BENCHMARK_OS_WINDOWS This is to avoid unused parameter warning-as-error * Added missing include for <vector> in perf_counters.cc * Moved doc to docs * Added license blurbs
2021-04-28 08:25:29 +00:00
# If successful, the following variables will be defined:
pfm: Use a more standard CMake approach for finding libpfm (#1628) * pfm: Use a more standard CMake approach for finding libpfm * add myself and sort AUTHORS & CONTRIBUTORS
2023-07-10 16:46:34 +00:00
# PFM_FOUND.
# PFM_LIBRARIES
# PFM_INCLUDE_DIRS
# the following target will be defined:
# PFM::libpfm
Support optional, user-directed collection of performance counters (#1114) * Support optional, user-directed collection of performance counters The patch allows an engineer wishing to drill into the root causes of a regression, for example. Currently, only single threaded runs are supported. The feature is a build-time opt in, and then a runtime opt in. The engineer may run the benchmark executable, passing a list of performance counter names (using libpfm's naming scheme) at the command line. The counter values will then be collected and reported back as UserCounters. This is different from #240 in that it is a benchmark user opt-in, and the counter collection is transparent to the benchmark. Currently, this is only supported on platforms where libpfm is supported. libpfm: http://perfmon2.sourceforge.net/ * 'Use' values param in Snapshot when BENCHMARK_OS_WINDOWS This is to avoid unused parameter warning-as-error * Added missing include for <vector> in perf_counters.cc * Moved doc to docs * Added license blurbs
2021-04-28 08:25:29 +00:00
missing cmake include
2023-07-10 16:58:01 +00:00
include(FeatureSummary)
pfm: Use a more standard CMake approach for finding libpfm (#1628) * pfm: Use a more standard CMake approach for finding libpfm * add myself and sort AUTHORS & CONTRIBUTORS
2023-07-10 16:46:34 +00:00
include(FindPackageHandleStandardArgs)
[NFC] PFM: actually report package as found, and advertise description This slightly prettifies the CMake's `feature_summary()` output, should the library be built as part of some project that then prints the CMake summary.
2021-08-23 16:36:34 +00:00
add back package properties for PFM
2023-07-10 16:54:09 +00:00
set_package_properties(PFM PROPERTIES
URL http://perfmon2.sourceforge.net/
DESCRIPTION "A helper library to develop monitoring tools"
PURPOSE "Used to program specific performance monitoring events")
pfm: Use a more standard CMake approach for finding libpfm (#1628) * pfm: Use a more standard CMake approach for finding libpfm * add myself and sort AUTHORS & CONTRIBUTORS
2023-07-10 16:46:34 +00:00
find_library(PFM_LIBRARY NAMES pfm)
find_path(PFM_INCLUDE_DIR NAMES perfmon/pfmlib.h)
find_package_handle_standard_args(PFM REQUIRED_VARS PFM_LIBRARY PFM_INCLUDE_DIR)
if (PFM_FOUND AND NOT TARGET PFM::libpfm)
add_library(PFM::libpfm UNKNOWN IMPORTED)
set_target_properties(PFM::libpfm PROPERTIES
IMPORTED_LOCATION "${PFM_LIBRARY}"
INTERFACE_INCLUDE_DIRECTORIES "${PFM_INCLUDE_DIR}")
Support optional, user-directed collection of performance counters (#1114) * Support optional, user-directed collection of performance counters The patch allows an engineer wishing to drill into the root causes of a regression, for example. Currently, only single threaded runs are supported. The feature is a build-time opt in, and then a runtime opt in. The engineer may run the benchmark executable, passing a list of performance counter names (using libpfm's naming scheme) at the command line. The counter values will then be collected and reported back as UserCounters. This is different from #240 in that it is a benchmark user opt-in, and the counter collection is transparent to the benchmark. Currently, this is only supported on platforms where libpfm is supported. libpfm: http://perfmon2.sourceforge.net/ * 'Use' values param in Snapshot when BENCHMARK_OS_WINDOWS This is to avoid unused parameter warning-as-error * Added missing include for <vector> in perf_counters.cc * Moved doc to docs * Added license blurbs
2021-04-28 08:25:29 +00:00
endif()
pfm: Use a more standard CMake approach for finding libpfm (#1628) * pfm: Use a more standard CMake approach for finding libpfm * add myself and sort AUTHORS & CONTRIBUTORS
2023-07-10 16:46:34 +00:00
mark_as_advanced(PFM_LIBRARY PFM_INCLUDE_DIR)