1bcbe65a8SJoseph Koshy.\" Copyright (c) 2003-2008 Joseph Koshy. All rights reserved. 2ebccf1e3SJoseph Koshy.\" 3ebccf1e3SJoseph Koshy.\" Redistribution and use in source and binary forms, with or without 4ebccf1e3SJoseph Koshy.\" modification, are permitted provided that the following conditions 5ebccf1e3SJoseph Koshy.\" are met: 6ebccf1e3SJoseph Koshy.\" 1. Redistributions of source code must retain the above copyright 7ebccf1e3SJoseph Koshy.\" notice, this list of conditions and the following disclaimer. 8ebccf1e3SJoseph Koshy.\" 2. Redistributions in binary form must reproduce the above copyright 9ebccf1e3SJoseph Koshy.\" notice, this list of conditions and the following disclaimer in the 10ebccf1e3SJoseph Koshy.\" documentation and/or other materials provided with the distribution. 11ebccf1e3SJoseph Koshy.\" 12ebccf1e3SJoseph Koshy.\" This software is provided by Joseph Koshy ``as is'' and 13ebccf1e3SJoseph Koshy.\" any express or implied warranties, including, but not limited to, the 14ebccf1e3SJoseph Koshy.\" implied warranties of merchantability and fitness for a particular purpose 15ebccf1e3SJoseph Koshy.\" are disclaimed. in no event shall Joseph Koshy be liable 16ebccf1e3SJoseph Koshy.\" for any direct, indirect, incidental, special, exemplary, or consequential 17ebccf1e3SJoseph Koshy.\" damages (including, but not limited to, procurement of substitute goods 18ebccf1e3SJoseph Koshy.\" or services; loss of use, data, or profits; or business interruption) 19ebccf1e3SJoseph Koshy.\" however caused and on any theory of liability, whether in contract, strict 20ebccf1e3SJoseph Koshy.\" liability, or tort (including negligence or otherwise) arising in any way 21ebccf1e3SJoseph Koshy.\" out of the use of this software, even if advised of the possibility of 22ebccf1e3SJoseph Koshy.\" such damage. 23ebccf1e3SJoseph Koshy.\" 24ebccf1e3SJoseph Koshy.\" $FreeBSD$ 25ebccf1e3SJoseph Koshy.\" 260f7668cbSJoseph Koshy.Dd November 24, 2008 27ebccf1e3SJoseph Koshy.Dt PMC 3 28aa12cea2SUlrich Spörlein.Os 29ebccf1e3SJoseph Koshy.Sh NAME 30c89d1cf5SJoseph Koshy.Nm pmc 31c89d1cf5SJoseph Koshy.Nd library for accessing hardware performance monitoring counters 32ebccf1e3SJoseph Koshy.Sh LIBRARY 33ebccf1e3SJoseph Koshy.Lb libpmc 34ebccf1e3SJoseph Koshy.Sh SYNOPSIS 35ebccf1e3SJoseph Koshy.In pmc.h 36ebccf1e3SJoseph Koshy.Sh DESCRIPTION 37ebccf1e3SJoseph KoshyThe 38c89d1cf5SJoseph Koshy.Lb libpmc 39c89d1cf5SJoseph Koshyprovides a programming interface that allows applications to use 40c89d1cf5SJoseph Koshyhardware performance counters to gather performance data about 41c89d1cf5SJoseph Koshyspecific processes or for the system as a whole. 42c89d1cf5SJoseph KoshyThe library is implemented using the lower-level facilities offered by 43c89d1cf5SJoseph Koshythe 44ebccf1e3SJoseph Koshy.Xr hwpmc 4 45c89d1cf5SJoseph Koshydriver. 46c89d1cf5SJoseph Koshy.Ss Key Concepts 47c89d1cf5SJoseph KoshyPerformance monitoring counters (PMCs) are represented by the library 48c89d1cf5SJoseph Koshyusing a software abstraction. 49c89d1cf5SJoseph KoshyThese 50c89d1cf5SJoseph Koshy.Dq abstract 51c2025a76SJoel DahlPMCs can have two scopes: 52c89d1cf5SJoseph Koshy.Bl -bullet 53c89d1cf5SJoseph Koshy.It 54c89d1cf5SJoseph KoshySystem scope. 55c89d1cf5SJoseph KoshyThese PMCs measure events in a whole-system manner, i.e., independent 56c89d1cf5SJoseph Koshyof the currently executing thread. 57c89d1cf5SJoseph KoshySystem scope PMCs are allocated on specific CPUs and do not 58c89d1cf5SJoseph Koshymigrate between CPUs. 59c89d1cf5SJoseph KoshyNon-privileged process are allowed to allocate system scope PMCs if the 60c89d1cf5SJoseph Koshy.Xr hwpmc 4 61c89d1cf5SJoseph Koshysysctl tunable: 62c89d1cf5SJoseph Koshy.Va security.bsd.unprivileged_syspmcs 63c89d1cf5SJoseph Koshyis non-zero. 64c89d1cf5SJoseph Koshy.It 65c89d1cf5SJoseph KoshyProcess scope. 66c89d1cf5SJoseph KoshyThese PMCs only measure hardware events when the processes they are 67c89d1cf5SJoseph Koshyattached to are executing on a CPU. 68c89d1cf5SJoseph KoshyIn an SMP system, process scope PMCs migrate between CPUs along with 69c89d1cf5SJoseph Koshytheir target processes. 70c89d1cf5SJoseph Koshy.El 71ebccf1e3SJoseph Koshy.Pp 72c89d1cf5SJoseph KoshyOrthogonal to PMC scope, PMCs may be allocated in one of two 73c89d1cf5SJoseph Koshyoperational modes: 74c89d1cf5SJoseph Koshy.Bl -bullet 75c89d1cf5SJoseph Koshy.It 76c89d1cf5SJoseph KoshyCounting PMCs measure events according to their scope 77c89d1cf5SJoseph Koshy(system or process). 78c89d1cf5SJoseph KoshyThe application needs to explicitly read these counters 79c89d1cf5SJoseph Koshyto retrieve their value. 80c89d1cf5SJoseph Koshy.It 81c89d1cf5SJoseph KoshySampling PMCs cause the CPU to be periodically interrupted 82c89d1cf5SJoseph Koshyand information about its state of execution to be collected. 83c89d1cf5SJoseph KoshySampling PMCs are used to profile specific processes and kernel 84c89d1cf5SJoseph Koshythreads or to profile the system as a whole. 85c89d1cf5SJoseph Koshy.El 86c89d1cf5SJoseph Koshy.Pp 87c89d1cf5SJoseph KoshyThe scope and operational mode for a software PMC are specified at 88c89d1cf5SJoseph KoshyPMC allocation time. 89c89d1cf5SJoseph KoshyAn application is allowed to allocate multiple PMCs subject 90c89d1cf5SJoseph Koshyto availability of hardware resources. 91c89d1cf5SJoseph Koshy.Pp 92c89d1cf5SJoseph KoshyThe library uses human-readable strings to name the event being 93c89d1cf5SJoseph Koshymeasured by hardware. 94c89d1cf5SJoseph KoshyThe syntax used for specifying a hardware event along with additional 95c89d1cf5SJoseph Koshyevent specific qualifiers (if any) is described in detail in section 96ebccf1e3SJoseph Koshy.Sx "EVENT SPECIFIERS" 97ebccf1e3SJoseph Koshybelow. 98ebccf1e3SJoseph Koshy.Pp 99c89d1cf5SJoseph KoshyPMCs are associated with the process that allocated them and 100c89d1cf5SJoseph Koshywill be automatically reclaimed by the system when the process exits. 101c89d1cf5SJoseph KoshyAdditionally, process-scope PMCs have to be attached to one or more 102c89d1cf5SJoseph Koshytarget processes before they can perform measurements. 103c89d1cf5SJoseph KoshyA process-scope PMC may be attached to those target processes 104c89d1cf5SJoseph Koshythat its owner process would otherwise be permitted to debug. 105c89d1cf5SJoseph KoshyAn owner process may attach PMCs to itself allowing 106c89d1cf5SJoseph Koshyit to measure its own behavior. 107c89d1cf5SJoseph KoshyAdditionally, on some machine architectures, such self-attached PMCs 108c89d1cf5SJoseph Koshymay be read cheaply using specialized instructions supported by the 109c89d1cf5SJoseph Koshyprocessor. 110ebccf1e3SJoseph Koshy.Pp 111c89d1cf5SJoseph KoshyCertain kinds of PMCs require that a log file be configured before 112c89d1cf5SJoseph Koshythey may be started. 113c89d1cf5SJoseph KoshyThese include: 114c89d1cf5SJoseph Koshy.Bl -bullet -compact 115c89d1cf5SJoseph Koshy.It 116c89d1cf5SJoseph KoshySystem scope sampling PMCs. 117c89d1cf5SJoseph Koshy.It 118c89d1cf5SJoseph KoshyProcess scope sampling PMCs. 119c89d1cf5SJoseph Koshy.It 120c89d1cf5SJoseph KoshyProcess scope counting PMCs that have been configured to report PMC 121c89d1cf5SJoseph Koshyreadings on process context switches or process exits. 122c89d1cf5SJoseph Koshy.El 123c89d1cf5SJoseph KoshyUp to one log file may be configured per owner process. 124c89d1cf5SJoseph KoshyEvents logged to a log file may be subsequently analyzed using the 125c89d1cf5SJoseph Koshy.Xr pmclog 3 126c89d1cf5SJoseph Koshyfamily of functions. 127c89d1cf5SJoseph Koshy.Ss Supported CPUs 128c89d1cf5SJoseph KoshyThe CPUs known to the PMC library are named by the 129c89d1cf5SJoseph Koshy.Vt "enum pmc_cputype" 130c89d1cf5SJoseph Koshyenumeration. 131c89d1cf5SJoseph KoshySupported CPUs include: 13280f30b73SJoseph Koshy.Bl -tag -width "Li PMC_CPU_INTEL_CORE2" -compact 13380f30b73SJoseph Koshy.It Li PMC_CPU_AMD_K7 134c89d1cf5SJoseph Koshy.Tn "AMD Athlon" 135c89d1cf5SJoseph KoshyCPUs. 13680f30b73SJoseph Koshy.It Li PMC_CPU_AMD_K8 137c89d1cf5SJoseph Koshy.Tn "AMD Athlon64" 138c89d1cf5SJoseph KoshyCPUs. 13980f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_ATOM 14080f30b73SJoseph Koshy.Tn Intel 14180f30b73SJoseph Koshy.Tn Atom 14280f30b73SJoseph KoshyCPUs and other CPUs conforming to version 3 of the 14380f30b73SJoseph Koshy.Tn Intel 14480f30b73SJoseph Koshyperformance measurement architecture. 14580f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_CORE 14680f30b73SJoseph Koshy.Tn Intel 14780f30b73SJoseph Koshy.Tn Core Solo 14880f30b73SJoseph Koshyand 14980f30b73SJoseph Koshy.Tn Core Duo 15080f30b73SJoseph KoshyCPUs, and other CPUs conforming to version 1 of the 15180f30b73SJoseph Koshy.Tn Intel 15280f30b73SJoseph Koshyperformance measurement architecture. 15380f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_CORE2 15480f30b73SJoseph Koshy.Tn Intel 15580f30b73SJoseph Koshy.Tn "Core2 Solo" , 15680f30b73SJoseph Koshy.Tn "Core2 Duo" 15780f30b73SJoseph Koshyand 15880f30b73SJoseph Koshy.Tn "Core2 Extreme" 15980f30b73SJoseph KoshyCPUs, and other CPUs conforming to version 2 of the 16080f30b73SJoseph Koshy.Tn Intel 16180f30b73SJoseph Koshyperformance measurement architecture. 16280f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_P5 163bcbe65a8SJoseph Koshy.Tn Intel 164bcbe65a8SJoseph Koshy.Tn "Pentium" 165bcbe65a8SJoseph KoshyCPUs. 16680f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_P6 167c89d1cf5SJoseph Koshy.Tn Intel 168c89d1cf5SJoseph Koshy.Tn "Pentium Pro" 169c89d1cf5SJoseph KoshyCPUs. 17080f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_PII 171c89d1cf5SJoseph Koshy.Tn "Intel Pentium II" 172c89d1cf5SJoseph KoshyCPUs. 17380f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_PIII 174c89d1cf5SJoseph Koshy.Tn "Intel Pentium III" 175c89d1cf5SJoseph KoshyCPUs. 17680f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_PIV 177c89d1cf5SJoseph Koshy.Tn "Intel Pentium 4" 178c89d1cf5SJoseph KoshyCPUs. 17980f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_PM 18080f30b73SJoseph Koshy.Tn "Intel Pentium M" 18180f30b73SJoseph KoshyCPUs. 182c89d1cf5SJoseph Koshy.El 183c89d1cf5SJoseph Koshy.Ss Supported PMCs 184c89d1cf5SJoseph KoshyPMC supported by this library are named by the 185c89d1cf5SJoseph Koshy.Vt enum pmc_class 186c89d1cf5SJoseph Koshyenumeration. 187c89d1cf5SJoseph KoshySupported PMC kinds include: 18872cf78b8SJoseph Koshy.Bl -tag -width "Li PMC_CLASS_IAF" -compact 18972cf78b8SJoseph Koshy.It Li PMC_CLASS_IAF 190f20a61ffSJoseph KoshyFixed function hardware counters presents in CPUs conforming to the 19180f30b73SJoseph Koshy.Tn Intel 19280f30b73SJoseph Koshyperformance measurement architecture version 2 and later. 19372cf78b8SJoseph Koshy.It Li PMC_CLASS_IAP 19472cf78b8SJoseph KoshyProgrammable hardware counters present in CPUs conforming to the 19572cf78b8SJoseph Koshy.Tn Intel 19672cf78b8SJoseph Koshyperformance measurement architecture version 1 and later. 19780f30b73SJoseph Koshy.It Li PMC_CLASS_K7 198c89d1cf5SJoseph KoshyProgrammable hardware counters present in 199c89d1cf5SJoseph Koshy.Tn "AMD Athlon" 200c89d1cf5SJoseph KoshyCPUs. 20180f30b73SJoseph Koshy.It Li PMC_CLASS_K8 202c89d1cf5SJoseph KoshyProgrammable hardware counters present in 203c89d1cf5SJoseph Koshy.Tn "AMD Athlon64" 204c89d1cf5SJoseph KoshyCPUs. 20580f30b73SJoseph Koshy.It Li PMC_CLASS_P4 20624f2c3f3SJoseph KoshyProgrammable hardware counters present in 20724f2c3f3SJoseph Koshy.Tn "Intel Pentium 4" 20824f2c3f3SJoseph KoshyCPUs. 20980f30b73SJoseph Koshy.It Li PMC_CLASS_P5 210bcbe65a8SJoseph KoshyProgrammable hardware counters present in 211bcbe65a8SJoseph Koshy.Tn Intel 212bcbe65a8SJoseph Koshy.Tn Pentium 213bcbe65a8SJoseph KoshyCPUs. 21480f30b73SJoseph Koshy.It Li PMC_CLASS_P6 215c89d1cf5SJoseph KoshyProgrammable hardware counters present in 216c89d1cf5SJoseph Koshy.Tn Intel 217c89d1cf5SJoseph Koshy.Tn "Pentium Pro" , 218c89d1cf5SJoseph Koshy.Tn "Pentium II" , 219c89d1cf5SJoseph Koshy.Tn "Pentium III" , 220c89d1cf5SJoseph Koshy.Tn "Celeron" , 221ebccf1e3SJoseph Koshyand 222c89d1cf5SJoseph Koshy.Tn "Pentium M" 223c89d1cf5SJoseph KoshyCPUs. 22480f30b73SJoseph Koshy.It Li PMC_CLASS_TSC 22524f2c3f3SJoseph KoshyThe timestamp counter on i386 and amd64 architecture CPUs. 226c89d1cf5SJoseph Koshy.El 227c89d1cf5SJoseph Koshy.Ss PMC Capabilities 228ebccf1e3SJoseph Koshy.Pp 229c89d1cf5SJoseph KoshyCapabilities of performance monitoring hardware are denoted using 230c89d1cf5SJoseph Koshythe 231c89d1cf5SJoseph Koshy.Vt "enum pmc_caps" 232c89d1cf5SJoseph Koshyenumeration. 233c89d1cf5SJoseph KoshySupported capabilities include: 23480f30b73SJoseph Koshy.Bl -tag -width "Li PMC_CAP_INTERRUPT" -compact 23580f30b73SJoseph Koshy.It Li PMC_CAP_CASCADE 23680f30b73SJoseph KoshyThe ability to cascade counters. 23780f30b73SJoseph Koshy.It Li PMC_CAP_EDGE 238c89d1cf5SJoseph KoshyThe ability to count negated to asserted transitions of the hardware 239c89d1cf5SJoseph Koshyconditions being probed for. 24080f30b73SJoseph Koshy.It Li PMC_CAP_INTERRUPT 241c89d1cf5SJoseph KoshyThe ability to interrupt the CPU. 24280f30b73SJoseph Koshy.It Li PMC_CAP_INVERT 243c89d1cf5SJoseph KoshyThe ability to invert the sense of the hardware conditions being 244c89d1cf5SJoseph Koshymeasured. 245624f6965SJoseph Koshy.It Li PMC_CAP_PRECISE 246624f6965SJoseph KoshyThe ability to perform precise sampling. 24780f30b73SJoseph Koshy.It Li PMC_CAP_QUALIFIER 248c89d1cf5SJoseph KoshyThe hardware allows monitored to be further qualified in some 249c89d1cf5SJoseph Koshysystem dependent way. 250624f6965SJoseph Koshy.It Li PMC_CAP_READ 251624f6965SJoseph KoshyThe ability to read from performance counters. 25280f30b73SJoseph Koshy.It Li PMC_CAP_SYSTEM 253c89d1cf5SJoseph KoshyThe ability to restrict counting of hardware events to when the CPU is 254c89d1cf5SJoseph Koshyrunning privileged code. 25580f30b73SJoseph Koshy.It Li PMC_CAP_THRESHOLD 256c89d1cf5SJoseph KoshyThe ability to ignore simultaneous hardware events below a 257c89d1cf5SJoseph Koshyprogrammable threshold. 25880f30b73SJoseph Koshy.It Li PMC_CAP_USER 259c89d1cf5SJoseph KoshyThe ability to restrict counting of hardware events to those when the 260c89d1cf5SJoseph KoshyCPU is running unprivileged code. 26180f30b73SJoseph Koshy.It Li PMC_CAP_WRITE 2620f3866faSJoseph KoshyThe ability to write to performance counters. 263c89d1cf5SJoseph Koshy.El 2646455febbSJoseph Koshy.Ss CPU Naming Conventions 265dd1259daSJoseph KoshyCPUs are named using small integers from zero up to, but 2666455febbSJoseph Koshyexcluding, the value returned by function 2676455febbSJoseph Koshy.Fn pmc_ncpu . 2686455febbSJoseph KoshyOn platforms supporting sparsely numbered CPUs not all the numbers in 2696455febbSJoseph Koshythis range will denote valid CPUs. 2706455febbSJoseph KoshyOperations on non-existent CPUs will return an error. 2716455febbSJoseph Koshy.Ss Functional Grouping of the API 272c89d1cf5SJoseph KoshyThis section contains a brief overview of the available functionality 273c89d1cf5SJoseph Koshyin the PMC library. 274c89d1cf5SJoseph KoshyEach function listed here is described further in its own manual page. 275c89d1cf5SJoseph Koshy.Bl -tag -width indent 276c89d1cf5SJoseph Koshy.It Administration 277c89d1cf5SJoseph Koshy.Bl -tag -compact 278c89d1cf5SJoseph Koshy.It Fn pmc_disable , Fn pmc_enable 279c89d1cf5SJoseph KoshyAdministratively disable (enable) specific performance monitoring 280c89d1cf5SJoseph Koshycounter hardware. 281c89d1cf5SJoseph KoshyCounters that are disabled will not be available to applications to 282c89d1cf5SJoseph Koshyuse. 283c89d1cf5SJoseph Koshy.El 284c89d1cf5SJoseph Koshy.It "Convenience Functions" 285c89d1cf5SJoseph Koshy.Bl -tag -compact 286c89d1cf5SJoseph Koshy.It Fn pmc_event_names_of_class 287c89d1cf5SJoseph KoshyReturns a list of event names supported by a given PMC type. 288c89d1cf5SJoseph Koshy.It Fn pmc_name_of_capability 289c89d1cf5SJoseph KoshyConvert a 290c89d1cf5SJoseph Koshy.Dv PMC_CAP_* 291c89d1cf5SJoseph Koshyflag to a human-readable string. 292c89d1cf5SJoseph Koshy.It Fn pmc_name_of_class 293c89d1cf5SJoseph KoshyConvert a 294c89d1cf5SJoseph Koshy.Dv PMC_CLASS_* 295c89d1cf5SJoseph Koshyconstant to a human-readable string. 296c89d1cf5SJoseph Koshy.It Fn pmc_name_of_cputype 297c89d1cf5SJoseph KoshyReturn a human-readable name for a CPU type. 298c89d1cf5SJoseph Koshy.It Fn pmc_name_of_disposition 299c89d1cf5SJoseph KoshyReturn a human-readable string describing a PMC's disposition. 300c89d1cf5SJoseph Koshy.It Fn pmc_name_of_event 301c89d1cf5SJoseph KoshyConvert a numeric event code to a human-readable string. 302c89d1cf5SJoseph Koshy.It Fn pmc_name_of_mode 303c89d1cf5SJoseph KoshyConvert a 304c89d1cf5SJoseph Koshy.Dv PMC_MODE_* 305c89d1cf5SJoseph Koshyconstant to a human-readable name. 306c89d1cf5SJoseph Koshy.It Fn pmc_name_of_state 307c89d1cf5SJoseph KoshyReturn a human-readable string describing a PMC's current state. 308c89d1cf5SJoseph Koshy.El 309c89d1cf5SJoseph Koshy.It "Library Initialization" 310c89d1cf5SJoseph Koshy.Bl -tag -compact 311c89d1cf5SJoseph Koshy.It Fn pmc_init 312c89d1cf5SJoseph KoshyInitialize the library. 313c89d1cf5SJoseph KoshyThis function must be called before any other library function. 314c89d1cf5SJoseph Koshy.El 315c89d1cf5SJoseph Koshy.It "Log File Handling" 316c89d1cf5SJoseph Koshy.Bl -tag -compact 317c89d1cf5SJoseph Koshy.It Fn pmc_configure_logfile 318c89d1cf5SJoseph KoshyConfigure a log file for 319c89d1cf5SJoseph Koshy.Xr hwpmc 4 320c89d1cf5SJoseph Koshyto write logged events to. 321c89d1cf5SJoseph Koshy.It Fn pmc_flush_logfile 322c89d1cf5SJoseph KoshyFlush all pending log data in 323c89d1cf5SJoseph Koshy.Xr hwpmc 4 Ns Ap s 324c89d1cf5SJoseph Koshybuffers. 325*dceed24aSFabien Thomas.It Fn pmc_close_logfile 326*dceed24aSFabien ThomasFlush all pending log data and close 327*dceed24aSFabien Thomas.Xr hwpmc 4 Ns Ap s 328*dceed24aSFabien Thomasside of the stream. 329c89d1cf5SJoseph Koshy.It Fn pmc_writelog 330c89d1cf5SJoseph KoshyAppend arbitrary user data to the current log file. 331c89d1cf5SJoseph Koshy.El 332c89d1cf5SJoseph Koshy.It "PMC Management" 333c89d1cf5SJoseph Koshy.Bl -tag -compact 334c89d1cf5SJoseph Koshy.It Fn pmc_allocate , Fn pmc_release 335c89d1cf5SJoseph KoshyAllocate (free) a PMC. 336c89d1cf5SJoseph Koshy.It Fn pmc_attach , Fn pmc_detach 337c89d1cf5SJoseph KoshyAttach (detach) a process scope PMC to a target. 338c89d1cf5SJoseph Koshy.It Fn pmc_read , Fn pmc_write , Fn pmc_rw 339c89d1cf5SJoseph KoshyRead (write) a value from (to) a PMC. 340c89d1cf5SJoseph Koshy.It Fn pmc_start , Fn pmc_stop 341c89d1cf5SJoseph KoshyStart (stop) a software PMC. 342c89d1cf5SJoseph Koshy.It Fn pmc_set 343c89d1cf5SJoseph KoshySet the reload value for a sampling PMC. 344c89d1cf5SJoseph Koshy.El 345c89d1cf5SJoseph Koshy.It "Queries" 346c89d1cf5SJoseph Koshy.Bl -tag -compact 347c89d1cf5SJoseph Koshy.It Fn pmc_capabilities 348c89d1cf5SJoseph KoshyRetrieve the capabilities for a given PMC. 349c89d1cf5SJoseph Koshy.It Fn pmc_cpuinfo 350c89d1cf5SJoseph KoshyRetrieve information about the CPUs and PMC hardware present in the 351c89d1cf5SJoseph Koshysystem. 352c89d1cf5SJoseph Koshy.It Fn pmc_get_driver_stats 353c89d1cf5SJoseph KoshyRetrieve statistics maintained by 354c89d1cf5SJoseph Koshy.Xr hwpmc 4 . 355c89d1cf5SJoseph Koshy.It Fn pmc_ncpu 3566455febbSJoseph KoshyDetermine the greatest possible CPU number on the system. 357c89d1cf5SJoseph Koshy.It Fn pmc_npmc 358c89d1cf5SJoseph KoshyReturn the number of hardware PMCs present in a given CPU. 359c89d1cf5SJoseph Koshy.It Fn pmc_pmcinfo 360c89d1cf5SJoseph KoshyReturn information about the state of a given CPU's PMCs. 361c89d1cf5SJoseph Koshy.It Fn pmc_width 362c89d1cf5SJoseph KoshyDetermine the width of a hardware counter in bits. 363c89d1cf5SJoseph Koshy.El 364c89d1cf5SJoseph Koshy.It "x86 Architecture Specific API" 365c89d1cf5SJoseph Koshy.Bl -tag -compact 366c89d1cf5SJoseph Koshy.It Fn pmc_get_msr 367c89d1cf5SJoseph KoshyReturns the processor model specific register number 368c89d1cf5SJoseph Koshyassociated with 369c5153e19SJoseph Koshy.Fa pmc . 370c89d1cf5SJoseph KoshyApplications may then use the x86 371c89d1cf5SJoseph Koshy.Ic RDPMC 372c89d1cf5SJoseph Koshyinstruction to directly read the contents of the PMC. 373c89d1cf5SJoseph Koshy.El 374c89d1cf5SJoseph Koshy.El 3759abe909bSRuslan Ermilov.Ss Signal Handling Requirements 376ebccf1e3SJoseph KoshyApplications using PMCs are required to handle the following signals: 377c89d1cf5SJoseph Koshy.Bl -tag -width ".Dv SIGBUS" 3789abe909bSRuslan Ermilov.It Dv SIGBUS 379ebccf1e3SJoseph KoshyWhen the 380ebccf1e3SJoseph Koshy.Xr hwpmc 4 381ebccf1e3SJoseph Koshymodule is unloaded using 382ebccf1e3SJoseph Koshy.Xr kldunload 8 , 383ebccf1e3SJoseph Koshyprocesses that have PMCs allocated to them will be sent a 3849abe909bSRuslan Ermilov.Dv SIGBUS 3859abe909bSRuslan Ermilovsignal. 3869abe909bSRuslan Ermilov.It Dv SIGIO 387f263522aSJoseph KoshyThe 388f263522aSJoseph Koshy.Xr hwpmc 4 3899abe909bSRuslan Ermilovdriver will send a PMC owning process a 3909abe909bSRuslan Ermilov.Dv SIGIO 3919abe909bSRuslan Ermilovsignal if: 392f263522aSJoseph Koshy.Bl -bullet 393f263522aSJoseph Koshy.It 394f263522aSJoseph KoshyIf any process-mode PMC allocated by it loses all its 395f263522aSJoseph Koshytarget processes. 396f263522aSJoseph Koshy.It 397f263522aSJoseph KoshyIf the driver encounters an error when writing log data to a 398f263522aSJoseph Koshyconfigured log file. 399f263522aSJoseph KoshyThis error may be retrieved by a subsequent call to 400f263522aSJoseph Koshy.Fn pmc_flush_logfile . 401f263522aSJoseph Koshy.El 402ebccf1e3SJoseph Koshy.El 403c89d1cf5SJoseph Koshy.Ss Typical Program Flow 404c89d1cf5SJoseph Koshy.Bl -enum 405c89d1cf5SJoseph Koshy.It 406c89d1cf5SJoseph KoshyAn application would first invoke function 407c89d1cf5SJoseph Koshy.Fn pmc_init 408c89d1cf5SJoseph Koshyto allow the library to initialize itself. 409c89d1cf5SJoseph Koshy.It 410c89d1cf5SJoseph KoshySignal handling would then be set up. 411c89d1cf5SJoseph Koshy.It 412c89d1cf5SJoseph KoshyNext the application would allocate the PMCs it desires using function 413c89d1cf5SJoseph Koshy.Fn pmc_allocate . 414c89d1cf5SJoseph Koshy.It 415c89d1cf5SJoseph KoshyInitial values for PMCs may be set using function 416c89d1cf5SJoseph Koshy.Fn pmc_set . 417c89d1cf5SJoseph Koshy.It 418c89d1cf5SJoseph KoshyIf a log file is necessary for the PMCs to work, it would 419c89d1cf5SJoseph Koshybe configured using function 420c89d1cf5SJoseph Koshy.Fn pmc_configure_logfile . 421c89d1cf5SJoseph Koshy.It 422c89d1cf5SJoseph KoshyProcess scope PMCs would then be attached to their target processes 423c89d1cf5SJoseph Koshyusing function 424c89d1cf5SJoseph Koshy.Fn pmc_attach . 425c89d1cf5SJoseph Koshy.It 426c89d1cf5SJoseph KoshyThe PMCs would then be started using function 427c89d1cf5SJoseph Koshy.Fn pmc_start . 428c89d1cf5SJoseph Koshy.It 429c89d1cf5SJoseph KoshyOnce started, the values of counting PMCs may be read using function 430b53a052dSJoseph Koshy.Fn pmc_read . 431c89d1cf5SJoseph KoshyFor PMCs that write events to the log file, this logged data would be 432c89d1cf5SJoseph Koshyread and parsed using the 433c89d1cf5SJoseph Koshy.Xr pmclog 3 434c89d1cf5SJoseph Koshyfamily of functions. 435c89d1cf5SJoseph Koshy.It 436c89d1cf5SJoseph KoshyPMCs are stopped using function 437c89d1cf5SJoseph Koshy.Fn pmc_stop , 438c89d1cf5SJoseph Koshyand process scope PMCs are detached from their targets using 439c89d1cf5SJoseph Koshyfunction 440c89d1cf5SJoseph Koshy.Fn pmc_detach . 441c89d1cf5SJoseph Koshy.It 442c89d1cf5SJoseph KoshyBefore the process exits, its may release its PMCs using function 443c89d1cf5SJoseph Koshy.Fn pmc_release . 444c89d1cf5SJoseph KoshyAny configured log file may be closed using function 445c89d1cf5SJoseph Koshy.Fn pmc_configure_logfile . 446c89d1cf5SJoseph Koshy.El 447ebccf1e3SJoseph Koshy.Sh EVENT SPECIFIERS 448ebccf1e3SJoseph KoshyEvent specifiers are strings comprising of an event name, followed by 449ebccf1e3SJoseph Koshyoptional parameters modifying the semantics of the hardware event 450ebccf1e3SJoseph Koshybeing probed. 4510b844226SJoseph KoshyEvent names are PMC architecture dependent, but the PMC library defines 4520b844226SJoseph Koshymachine independent aliases for commonly used events. 4530f7668cbSJoseph Koshy.Pp 4540f7668cbSJoseph KoshyEvent specifiers spellings are case-insensitive and space characters, 4550f7668cbSJoseph Koshyperiods, underscores and hyphens are considered equivalent to each other. 4560f7668cbSJoseph KoshyThus the event specifiers 4570f7668cbSJoseph Koshy.Qq "Example Event" , 4580f7668cbSJoseph Koshy.Qq "example-event" , 4590f7668cbSJoseph Koshyand 4600f7668cbSJoseph Koshy.Qq "EXAMPLE_EVENT" 4610f7668cbSJoseph Koshyare equivalent. 4620f7668cbSJoseph Koshy.Ss PMC Architecture Dependent Events 4630f7668cbSJoseph KoshyPMC architecture dependent event specifiers are described in the 4640f7668cbSJoseph Koshyfollowing manual pages: 4650f7668cbSJoseph Koshy.Bl -column " PMC_CLASS_TSC " "MANUAL PAGE " 4660f7668cbSJoseph Koshy.It Em "PMC Class" Ta Em "Manual Page" 4670f7668cbSJoseph Koshy.It Li PMC_CLASS_IAF Ta Xr pmc.iaf 3 4680f7668cbSJoseph Koshy.It Li PMC_CLASS_IAP Ta Xr pmc.atom 3 , Xr pmc.core 3 , Xr pmc.core2 3 4690f7668cbSJoseph Koshy.It Li PMC_CLASS_K7 Ta Xr pmc.k7 3 4700f7668cbSJoseph Koshy.It Li PMC_CLASS_K8 Ta Xr pmc.k8 3 4710f7668cbSJoseph Koshy.It Li PMC_CLASS_P4 Ta Xr pmc.p4 3 4720f7668cbSJoseph Koshy.It Li PMC_CLASS_P5 Ta Xr pmc.p5 3 4730f7668cbSJoseph Koshy.It Li PMC_CLASS_P6 Ta Xr pmc.p6 3 4740f7668cbSJoseph Koshy.It Li PMC_CLASS_TSC Ta Xr pmc.tsc 3 4750f7668cbSJoseph Koshy.El 476ebccf1e3SJoseph Koshy.Ss Event Name Aliases 47724f2c3f3SJoseph KoshyEvent name aliases are PMC-independent names for commonly used events. 478ebccf1e3SJoseph KoshyThe following aliases are known to this version of the 479110e1704SRuslan Ermilov.Nm pmc 480ebccf1e3SJoseph Koshylibrary: 481ebccf1e3SJoseph Koshy.Bl -tag -width indent 482ebccf1e3SJoseph Koshy.It Li branches 483ebccf1e3SJoseph KoshyMeasure the number of branches retired. 484ebccf1e3SJoseph Koshy.It Li branch-mispredicts 485ebccf1e3SJoseph KoshyMeasure the number of retired branches that were mispredicted. 486ebccf1e3SJoseph Koshy.It Li cycles 487ebccf1e3SJoseph KoshyMeasure processor cycles. 488ebccf1e3SJoseph KoshyThis event is implemented using the processor's Time Stamp Counter 489ebccf1e3SJoseph Koshyregister. 490ebccf1e3SJoseph Koshy.It Li dc-misses 491ebccf1e3SJoseph KoshyMeasure the number of data cache misses. 492ebccf1e3SJoseph Koshy.It Li ic-misses 493ebccf1e3SJoseph KoshyMeasure the number of instruction cache misses. 494ebccf1e3SJoseph Koshy.It Li instructions 495ebccf1e3SJoseph KoshyMeasure the number of instructions retired. 496ebccf1e3SJoseph Koshy.It Li interrupts 497ebccf1e3SJoseph KoshyMeasure the number of interrupts seen. 498177a2f22SJoseph Koshy.It Li unhalted-cycles 499177a2f22SJoseph KoshyMeasure the number of cycles the processor is not in a halted 500177a2f22SJoseph Koshyor sleep state. 501ebccf1e3SJoseph Koshy.El 5025138c36aSJoseph Koshy.Sh COMPATIBILITY 5035138c36aSJoseph KoshyThe interface between the 504110e1704SRuslan Ermilov.Nm pmc 5055138c36aSJoseph Koshylibrary and the 5065138c36aSJoseph Koshy.Xr hwpmc 4 5075138c36aSJoseph Koshydriver is intended to be private to the implementation and may 5085138c36aSJoseph Koshychange. 5095138c36aSJoseph KoshyIn order to ease forward compatibility with future versions of the 5105138c36aSJoseph Koshy.Xr hwpmc 4 5115138c36aSJoseph Koshydriver, applications are urged to dynamically link with the 512110e1704SRuslan Ermilov.Nm pmc 5135138c36aSJoseph Koshylibrary. 5145138c36aSJoseph Koshy.Pp 5155138c36aSJoseph KoshyThe 516110e1704SRuslan Ermilov.Nm pmc 5175138c36aSJoseph KoshyAPI is 5185138c36aSJoseph Koshy.Ud 519ebccf1e3SJoseph Koshy.Sh SEE ALSO 52072cf78b8SJoseph Koshy.Xr pmc.atom 3 , 52172cf78b8SJoseph Koshy.Xr pmc.core 3 , 52272cf78b8SJoseph Koshy.Xr pmc.core2 3 , 52372cf78b8SJoseph Koshy.Xr pmc.iaf 3 , 52424f2c3f3SJoseph Koshy.Xr pmc.k7 3 , 52524f2c3f3SJoseph Koshy.Xr pmc.k8 3 , 52624f2c3f3SJoseph Koshy.Xr pmc.p4 3 , 52724f2c3f3SJoseph Koshy.Xr pmc.p5 3 , 52824f2c3f3SJoseph Koshy.Xr pmc.p6 3 , 52924f2c3f3SJoseph Koshy.Xr pmc.tsc 3 , 530f263522aSJoseph Koshy.Xr pmclog 3 , 531ebccf1e3SJoseph Koshy.Xr hwpmc 4 , 532ebccf1e3SJoseph Koshy.Xr pmccontrol 8 , 533ebccf1e3SJoseph Koshy.Xr pmcstat 8 5345138c36aSJoseph Koshy.Sh HISTORY 5355138c36aSJoseph KoshyThe 536110e1704SRuslan Ermilov.Nm pmc 5375138c36aSJoseph Koshylibrary first appeared in 5385138c36aSJoseph Koshy.Fx 6.0 . 539c89d1cf5SJoseph Koshy.Sh AUTHORS 540c89d1cf5SJoseph KoshyThe 541c89d1cf5SJoseph Koshy.Lb libpmc 542c89d1cf5SJoseph Koshylibrary was written by 543c89d1cf5SJoseph Koshy.An "Joseph Koshy" 544c89d1cf5SJoseph Koshy.Aq jkoshy@FreeBSD.org . 545