1.\" Copyright (c) 2003-2008 Joseph Koshy. All rights reserved. 2.\" 3.\" Redistribution and use in source and binary forms, with or without 4.\" modification, are permitted provided that the following conditions 5.\" are met: 6.\" 1. Redistributions of source code must retain the above copyright 7.\" notice, this list of conditions and the following disclaimer. 8.\" 2. Redistributions in binary form must reproduce the above copyright 9.\" notice, this list of conditions and the following disclaimer in the 10.\" documentation and/or other materials provided with the distribution. 11.\" 12.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND 13.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 14.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 15.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 16.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 17.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 18.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 19.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 20.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 21.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 22.\" SUCH DAMAGE. 23.\" 24.Dd June 23, 2023 25.Dt PMC 3 26.Os 27.Sh NAME 28.Nm pmc 29.Nd library for accessing hardware performance monitoring counters 30.Sh LIBRARY 31.Lb libpmc 32.Sh SYNOPSIS 33.In pmc.h 34.Sh DESCRIPTION 35The 36.Lb libpmc 37provides a programming interface that allows applications to use 38hardware performance counters to gather performance data about 39specific processes or for the system as a whole. 40The library is implemented using the lower-level facilities offered by 41the 42.Xr hwpmc 4 43driver. 44.Ss Key Concepts 45Performance monitoring counters (PMCs) are represented by the library 46using a software abstraction. 47These 48.Dq abstract 49PMCs can have two scopes: 50.Bl -bullet 51.It 52System scope. 53These PMCs measure events in a whole-system manner, i.e., independent 54of the currently executing thread. 55System scope PMCs are allocated on specific CPUs and do not 56migrate between CPUs. 57Non-privileged process are allowed to allocate system scope PMCs if the 58.Xr hwpmc 4 59sysctl tunable: 60.Va security.bsd.unprivileged_syspmcs 61is non-zero. 62.It 63Process scope. 64These PMCs only measure hardware events when the processes they are 65attached to are executing on a CPU. 66In an SMP system, process scope PMCs migrate between CPUs along with 67their target processes. 68.El 69.Pp 70Orthogonal to PMC scope, PMCs may be allocated in one of two 71operational modes: 72.Bl -bullet 73.It 74Counting PMCs measure events according to their scope 75(system or process). 76The application needs to explicitly read these counters 77to retrieve their value. 78.It 79Sampling PMCs cause the CPU to be periodically interrupted 80and information about its state of execution to be collected. 81Sampling PMCs are used to profile specific processes and kernel 82threads or to profile the system as a whole. 83.El 84.Pp 85The scope and operational mode for a software PMC are specified at 86PMC allocation time. 87An application is allowed to allocate multiple PMCs subject 88to availability of hardware resources. 89.Pp 90The library uses human-readable strings to name the event being 91measured by hardware. 92The syntax used for specifying a hardware event along with additional 93event specific qualifiers (if any) is described in detail in section 94.Sx "EVENT SPECIFIERS" 95below. 96.Pp 97PMCs are associated with the process that allocated them and 98will be automatically reclaimed by the system when the process exits. 99Additionally, process-scope PMCs have to be attached to one or more 100target processes before they can perform measurements. 101A process-scope PMC may be attached to those target processes 102that its owner process would otherwise be permitted to debug. 103An owner process may attach PMCs to itself allowing 104it to measure its own behavior. 105Additionally, on some machine architectures, such self-attached PMCs 106may be read cheaply using specialized instructions supported by the 107processor. 108.Pp 109Certain kinds of PMCs require that a log file be configured before 110they may be started. 111These include: 112.Bl -bullet 113.It 114System scope sampling PMCs. 115.It 116Process scope sampling PMCs. 117.It 118Process scope counting PMCs that have been configured to report PMC 119readings on process context switches or process exits. 120.El 121.Pp 122Up to one log file may be configured per owner process. 123Events logged to a log file may be subsequently analyzed using the 124.Xr pmclog 3 125family of functions. 126.Ss Supported CPUs 127The CPUs known to the PMC library are named by the 128.Vt "enum pmc_cputype" 129enumeration. 130Supported CPUs include: 131.Pp 132.Bl -tag -width "Li PMC_CPU_ARMV7_CORTEX_A15" -compact 133.It Li PMC_CPU_AMD_K8 134.Tn "AMD Athlon64" 135CPUs. 136.It Li PMC_CPU_ARMV7_CORTEX_A5 137.Tn ARMv7 138.Tn Cortex A5 139CPUs. 140.It Li PMC_CPU_ARMV7_CORTEX_A7 141.Tn ARMv7 142.Tn Cortex A7 143CPUs. 144.It Li PMC_CPU_ARMV7_CORTEX_A8 145.Tn ARMv7 146.Tn Cortex A8 147CPUs. 148.It Li PMC_CPU_ARMV7_CORTEX_A9 149.Tn ARMv7 150.Tn Cortex A9 151CPUs. 152.It Li PMC_CPU_ARMV7_CORTEX_A15 153.Tn ARMv7 Cortex A15 154CPUs. 155.It Li PMC_CPU_ARMV7_CORTEX_A17 156.Tn ARMv7 157.Tn Cortex A17 158CPUs. 159.It Li PMC_CPU_ARMV8_CORTEX_A53 160ARMv8 161.Tn Cortex A53 162CPUs. 163.It Li PMC_CPU_ARMV8_CORTEX_A57 164ARMv8 165.Tn Cortex A57 166CPUs. 167.It Li PMC_CPU_ARMV8_CORTEX_A76 168ARMv8 169.Tn Cortex A76 170CPUs. 171.It Li GENERIC 172Generic 173.It Li PMC_CPU_INTEL_ATOM 174.Tn Intel 175.Tn Atom 176CPUs and other CPUs conforming to version 3 of the 177.Tn Intel 178performance measurement architecture. 179.It Li PMC_CPU_INTEL_CORE 180.Tn Intel 181.Tn Core Solo 182and 183.Tn Core Duo 184CPUs, and other CPUs conforming to version 1 of the 185.Tn Intel 186performance measurement architecture. 187.It Li PMC_CPU_INTEL_CORE2 188.Tn Intel 189.Tn "Core2 Solo" , 190.Tn "Core2 Duo" 191and 192.Tn "Core2 Extreme" 193CPUs, and other CPUs conforming to version 2 of the 194.Tn Intel 195performance measurement architecture. 196.It Li PMC_CPU_PPC_7450 197.Tn PowerPC 198MPC7450 CPUs. 199.It Li PMC_CPU_PPC_970 200.Tn IBM 201.Tn PowerPC 202970 CPUs. 203.It Li PMC_CPU_PPC_E500 204.Tn PowerPC 205e500 Core CPUs. 206.It Li PMC_CPU_PPC_POWER8 207.Tn IBM 208.Tn POWER8 and 209.Tn POWER9 210CPUs. 211.El 212.Ss Supported PMCs 213PMCs supported by this library are named by the 214.Vt enum pmc_class 215enumeration. 216Supported PMC classes include: 217.Pp 218.Bl -tag -width "Li PMC_CLASS_POWER8" -compact 219.It Li PMC_CLASS_IAF 220Fixed function hardware counters presents in CPUs conforming to the 221.Tn Intel 222performance measurement architecture version 2 and later. 223.It Li PMC_CLASS_IAP 224Programmable hardware counters present in CPUs conforming to the 225.Tn Intel 226performance measurement architecture version 1 and later. 227.It Li PMC_CLASS_IBS 228.Tn AMD 229Instruction Based Sampling (IBS) counters present in 230.Tn AMD 231Family 10h and above. 232.It Li PMC_CLASS_K8 233Programmable hardware counters present in 234.Tn "AMD Athlon64" 235CPUs. 236.It Li PMC_CLASS_RAPL 237RAPL energy counters present in 238.Tn AMD 239and 240.Tn Intel 241CPUs. 242.It Li PMC_CLASS_TSC 243The timestamp counter on i386 and amd64 architecture CPUs. 244.It Li PMC_CLASS_ARMV7 245.Tn ARMv7 246.It Li PMC_CLASS_ARMV8 247.Tn ARMv8 248.It Li PMC_CLASS_PPC970 249.Tn IBM 250.Tn PowerPC 251970 class. 252.It Li PMC_CLASS_POWER8 253.Tn IBM 254.Tn POWER8 255class. 256.It Li PMC_CLASS_SOFT 257Software events. 258.El 259.Ss PMC Capabilities 260Capabilities of performance monitoring hardware are denoted using 261the 262.Vt "enum pmc_caps" 263enumeration. 264Supported capabilities include: 265.Pp 266.Bl -tag -width "Li PMC_CAP_INTERRUPT" -compact 267.It Li PMC_CAP_CASCADE 268The ability to cascade counters. 269.It Li PMC_CAP_DOMWIDE 270Separate counters tied to each NUMA domain. 271.It Li PMC_CAP_EDGE 272The ability to count negated to asserted transitions of the hardware 273conditions being probed for. 274.It Li PMC_CAP_INTERRUPT 275The ability to interrupt the CPU. 276.It Li PMC_CAP_INVERT 277The ability to invert the sense of the hardware conditions being 278measured. 279.It Li PMC_CAP_PRECISE 280The ability to perform precise sampling. 281.It Li PMC_CAP_QUALIFIER 282The hardware allows monitored to be further qualified in some 283system dependent way. 284.It Li PMC_CAP_READ 285The ability to read from performance counters. 286.It Li PMC_CAP_SYSTEM 287The ability to restrict counting of hardware events to when the CPU is 288running privileged code. 289.It Li PMC_CAP_SYSWIDE 290A single counter aggregating events for the whole system. 291.It Li PMC_CAP_THRESHOLD 292The ability to ignore simultaneous hardware events below a 293programmable threshold. 294.It Li PMC_CAP_USER 295The ability to restrict counting of hardware events to those when the 296CPU is running unprivileged code. 297.It Li PMC_CAP_WRITE 298The ability to write to performance counters. 299.El 300.Ss CPU Naming Conventions 301CPUs are named using small integers from zero up to, but 302excluding, the value returned by function 303.Fn pmc_ncpu . 304On platforms supporting sparsely numbered CPUs not all the numbers in 305this range will denote valid CPUs. 306Operations on non-existent CPUs will return an error. 307.Ss Functional Grouping of the API 308This section contains a brief overview of the available functionality 309in the PMC library. 310Each function listed here is described further in its own manual page. 311.Bl -tag -width 2n 312.It Administration 313.Bl -tag -width 6n -compact 314.It Fn pmc_disable , Fn pmc_enable 315Administratively disable (enable) specific performance monitoring 316counter hardware. 317Counters that are disabled will not be available to applications to 318use. 319.El 320.It "Convenience Functions" 321.Bl -tag -width 6n -compact 322.It Fn pmc_event_names_of_class 323Returns a list of event names supported by a given PMC type. 324.It Fn pmc_name_of_capability 325Convert a 326.Dv PMC_CAP_* 327flag to a human-readable string. 328.It Fn pmc_name_of_class 329Convert a 330.Dv PMC_CLASS_* 331constant to a human-readable string. 332.It Fn pmc_name_of_cputype 333Return a human-readable name for a CPU type. 334.It Fn pmc_name_of_disposition 335Return a human-readable string describing a PMC's disposition. 336.It Fn pmc_name_of_event 337Convert a numeric event code to a human-readable string. 338.It Fn pmc_name_of_mode 339Convert a 340.Dv PMC_MODE_* 341constant to a human-readable name. 342.It Fn pmc_name_of_state 343Return a human-readable string describing a PMC's current state. 344.El 345.It "Library Initialization" 346.Bl -tag -width 6n -compact 347.It Fn pmc_init 348Initialize the library. 349This function must be called before any other library function. 350.El 351.It "Log File Handling" 352.Bl -tag -width 6n -compact 353.It Fn pmc_configure_logfile 354Configure a log file for 355.Xr hwpmc 4 356to write logged events to. 357.It Fn pmc_flush_logfile 358Flush all pending log data in 359.Xr hwpmc 4 Ns Ap s 360buffers. 361.It Fn pmc_close_logfile 362Flush all pending log data and close 363.Xr hwpmc 4 Ns Ap s 364side of the stream. 365.It Fn pmc_writelog 366Append arbitrary user data to the current log file. 367.El 368.It "PMC Management" 369.Bl -tag -width 6n -compact 370.It Fn pmc_allocate , Fn pmc_release 371Allocate (free) a PMC. 372.It Fn pmc_attach , Fn pmc_detach 373Attach (detach) a process scope PMC to a target. 374.It Fn pmc_read , Fn pmc_write , Fn pmc_rw 375Read (write) a value from (to) a PMC. 376.It Fn pmc_start , Fn pmc_stop 377Start (stop) a software PMC. 378.It Fn pmc_set 379Set the reload value for a sampling PMC. 380.El 381.It "Queries" 382.Bl -tag -width 6n -compact 383.It Fn pmc_capabilities 384Retrieve the capabilities for a given PMC. 385.It Fn pmc_cpuinfo 386Retrieve information about the CPUs and PMC hardware present in the 387system. 388.It Fn pmc_get_driver_stats 389Retrieve statistics maintained by 390.Xr hwpmc 4 . 391.It Fn pmc_ncpu 392Determine the greatest possible CPU number on the system. 393.It Fn pmc_npmc 394Return the number of hardware PMCs present in a given CPU. 395.It Fn pmc_pmcinfo 396Return information about the state of a given CPU's PMCs. 397.It Fn pmc_width 398Determine the width of a hardware counter in bits. 399.El 400.It "x86 Architecture Specific API" 401.Bl -tag -width 6n -compact 402.It Fn pmc_get_msr 403Returns the processor model specific register number 404associated with 405.Fa pmc . 406Applications may then use the x86 407.Ic RDPMC 408instruction to directly read the contents of the PMC. 409.El 410.El 411.Ss Signal Handling Requirements 412Applications using PMCs are required to handle the following signals: 413.Bl -tag -width ".Dv SIGBUS" 414.It Dv SIGBUS 415When the 416.Xr hwpmc 4 417module is unloaded using 418.Xr kldunload 8 , 419processes that have PMCs allocated to them will be sent a 420.Dv SIGBUS 421signal. 422.It Dv SIGIO 423The 424.Xr hwpmc 4 425driver will send a PMC owning process a 426.Dv SIGIO 427signal if: 428.Bl -bullet 429.It 430any process-mode PMC allocated by it loses all its 431target processes. 432.It 433the driver encounters an error when writing log data to a 434configured log file. 435This error may be retrieved by a subsequent call to 436.Fn pmc_flush_logfile . 437.El 438.El 439.Ss Typical Program Flow 440.Bl -enum 441.It 442An application would first invoke function 443.Fn pmc_init 444to allow the library to initialize itself. 445.It 446Signal handling would then be set up. 447.It 448Next the application would allocate the PMCs it desires using function 449.Fn pmc_allocate . 450.It 451Initial values for PMCs may be set using function 452.Fn pmc_set . 453.It 454If a log file is necessary for the PMCs to work, it would 455be configured using function 456.Fn pmc_configure_logfile . 457.It 458Process scope PMCs would then be attached to their target processes 459using function 460.Fn pmc_attach . 461.It 462The PMCs would then be started using function 463.Fn pmc_start . 464.It 465Once started, the values of counting PMCs may be read using function 466.Fn pmc_read . 467For PMCs that write events to the log file, this logged data would be 468read and parsed using the 469.Xr pmclog 3 470family of functions. 471.It 472PMCs are stopped using function 473.Fn pmc_stop , 474and process scope PMCs are detached from their targets using 475function 476.Fn pmc_detach . 477.It 478Before the process exits, it may release its PMCs using function 479.Fn pmc_release . 480Any configured log file may be closed using function 481.Fn pmc_configure_logfile . 482.El 483.Sh EVENT SPECIFIERS 484Event specifiers are strings comprising of an event name, followed by 485optional parameters modifying the semantics of the hardware event 486being probed. 487Event names are PMC architecture dependent, but the PMC library defines 488machine independent aliases for commonly used events. 489.Pp 490Event specifiers spellings are case-insensitive and space characters, 491periods, underscores and hyphens are considered equivalent to each other. 492Thus the event specifiers 493.Qq "Example Event" , 494.Qq "example-event" , 495and 496.Qq "EXAMPLE_EVENT" 497are equivalent. 498.Ss PMC Architecture Dependent Events 499PMC architecture dependent event specifiers are described in the 500following manual pages: 501.Bl -column " PMC_CLASS_TSC " "MANUAL PAGE " 502.It Em "PMC Class" Ta Em "Manual Page" 503.It Li PMC_CLASS_IAF Ta Xr pmc.iaf 3 504.It Li PMC_CLASS_IAP Ta Xr pmc.atom 3 , Xr pmc.core 3 , Xr pmc.core2 3 505.It Li PMC_CLASS_IBS Ta Xr pmc.ibs 3 506.It Li PMC_CLASS_K8 Ta Xr pmc.amd 3 507.It Li PMC_CLASS_RAPL Ta Xr pmc.rapl 3 508.It Li PMC_CLASS_TSC Ta Xr pmc.tsc 3 509.El 510.Ss Event Name Aliases 511Event name aliases are PMC-independent names for commonly used events. 512The following aliases are known to this version of the 513.Nm pmc 514library: 515.Bl -tag -width indent 516.It Li branches 517Measure the number of branches retired. 518.It Li branch-mispredicts 519Measure the number of retired branches that were mispredicted. 520.It Li cycles 521Measure processor cycles. 522This event is implemented using the processor's Time Stamp Counter 523register. 524.It Li dc-misses 525Measure the number of data cache misses. 526.It Li ic-misses 527Measure the number of instruction cache misses. 528.It Li instructions 529Measure the number of instructions retired. 530.It Li interrupts 531Measure the number of interrupts seen. 532.It Li unhalted-cycles 533Measure the number of cycles the processor is not in a halted 534or sleep state. 535.El 536.Sh COMPATIBILITY 537The interface between the 538.Nm pmc 539library and the 540.Xr hwpmc 4 541driver is intended to be private to the implementation and may 542change. 543In order to ease forward compatibility with future versions of the 544.Xr hwpmc 4 545driver, applications are urged to dynamically link with the 546.Nm pmc 547library. 548Doing otherwise is unsupported. 549.Sh SEE ALSO 550.Xr pmc.amd 3 , 551.Xr pmc.atom 3 , 552.Xr pmc.core 3 , 553.Xr pmc.core2 3 , 554.Xr pmc.haswell 3 , 555.Xr pmc.haswelluc 3 , 556.Xr pmc.haswellxeon 3 , 557.Xr pmc.iaf 3 , 558.Xr pmc.ibs 3 , 559.Xr pmc.ivybridge 3 , 560.Xr pmc.ivybridgexeon 3 , 561.Xr pmc.rapl 3 , 562.Xr pmc.sandybridge 3 , 563.Xr pmc.sandybridgeuc 3 , 564.Xr pmc.sandybridgexeon 3 , 565.Xr pmc.soft 3 , 566.Xr pmc.tsc 3 , 567.Xr pmc.westmere 3 , 568.Xr pmc.westmereuc 3 , 569.Xr pmc_allocate 3 , 570.Xr pmc_attach 3 , 571.Xr pmc_capabilities 3 , 572.Xr pmc_configure_logfile 3 , 573.Xr pmc_disable 3 , 574.Xr pmc_event_names_of_class 3 , 575.Xr pmc_get_driver_stats 3 , 576.Xr pmc_get_msr 3 , 577.Xr pmc_init 3 , 578.Xr pmc_name_of_capability 3 , 579.Xr pmc_read 3 , 580.Xr pmc_set 3 , 581.Xr pmc_start 3 , 582.Xr pmclog 3 , 583.Xr hwpmc 4 , 584.Xr pmccontrol 8 , 585.Xr pmcstat 8 586.Sh HISTORY 587The 588.Nm pmc 589library first appeared in 590.Fx 6.0 . 591.Sh AUTHORS 592The 593.Lb libpmc 594library was written by 595.An Joseph Koshy Aq Mt jkoshy@FreeBSD.org . 596