xref: /freebsd/lib/libpmc/pmc.3 (revision 61e21613)
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_K8
228Programmable hardware counters present in
229.Tn "AMD Athlon64"
230CPUs.
231.It Li PMC_CLASS_TSC
232The timestamp counter on i386 and amd64 architecture CPUs.
233.It Li PMC_CLASS_ARMV7
234.Tn ARMv7
235.It Li PMC_CLASS_ARMV8
236.Tn ARMv8
237.It Li PMC_CLASS_PPC970
238.Tn IBM
239.Tn PowerPC
240970 class.
241.It Li PMC_CLASS_POWER8
242.Tn IBM
243.Tn POWER8
244class.
245.It Li PMC_CLASS_SOFT
246Software events.
247.El
248.Ss PMC Capabilities
249Capabilities of performance monitoring hardware are denoted using
250the
251.Vt "enum pmc_caps"
252enumeration.
253Supported capabilities include:
254.Pp
255.Bl -tag -width "Li PMC_CAP_INTERRUPT" -compact
256.It Li PMC_CAP_CASCADE
257The ability to cascade counters.
258.It Li PMC_CAP_DOMWIDE
259Separate counters tied to each NUMA domain.
260.It Li PMC_CAP_EDGE
261The ability to count negated to asserted transitions of the hardware
262conditions being probed for.
263.It Li PMC_CAP_INTERRUPT
264The ability to interrupt the CPU.
265.It Li PMC_CAP_INVERT
266The ability to invert the sense of the hardware conditions being
267measured.
268.It Li PMC_CAP_PRECISE
269The ability to perform precise sampling.
270.It Li PMC_CAP_QUALIFIER
271The hardware allows monitored to be further qualified in some
272system dependent way.
273.It Li PMC_CAP_READ
274The ability to read from performance counters.
275.It Li PMC_CAP_SYSTEM
276The ability to restrict counting of hardware events to when the CPU is
277running privileged code.
278.It Li PMC_CAP_SYSWIDE
279A single counter aggregating events for the whole system.
280.It Li PMC_CAP_THRESHOLD
281The ability to ignore simultaneous hardware events below a
282programmable threshold.
283.It Li PMC_CAP_USER
284The ability to restrict counting of hardware events to those when the
285CPU is running unprivileged code.
286.It Li PMC_CAP_WRITE
287The ability to write to performance counters.
288.El
289.Ss CPU Naming Conventions
290CPUs are named using small integers from zero up to, but
291excluding, the value returned by function
292.Fn pmc_ncpu .
293On platforms supporting sparsely numbered CPUs not all the numbers in
294this range will denote valid CPUs.
295Operations on non-existent CPUs will return an error.
296.Ss Functional Grouping of the API
297This section contains a brief overview of the available functionality
298in the PMC library.
299Each function listed here is described further in its own manual page.
300.Bl -tag -width 2n
301.It Administration
302.Bl -tag -width 6n -compact
303.It Fn pmc_disable , Fn pmc_enable
304Administratively disable (enable) specific performance monitoring
305counter hardware.
306Counters that are disabled will not be available to applications to
307use.
308.El
309.It "Convenience Functions"
310.Bl -tag -width 6n -compact
311.It Fn pmc_event_names_of_class
312Returns a list of event names supported by a given PMC type.
313.It Fn pmc_name_of_capability
314Convert a
315.Dv PMC_CAP_*
316flag to a human-readable string.
317.It Fn pmc_name_of_class
318Convert a
319.Dv PMC_CLASS_*
320constant to a human-readable string.
321.It Fn pmc_name_of_cputype
322Return a human-readable name for a CPU type.
323.It Fn pmc_name_of_disposition
324Return a human-readable string describing a PMC's disposition.
325.It Fn pmc_name_of_event
326Convert a numeric event code to a human-readable string.
327.It Fn pmc_name_of_mode
328Convert a
329.Dv PMC_MODE_*
330constant to a human-readable name.
331.It Fn pmc_name_of_state
332Return a human-readable string describing a PMC's current state.
333.El
334.It "Library Initialization"
335.Bl -tag -width 6n -compact
336.It Fn pmc_init
337Initialize the library.
338This function must be called before any other library function.
339.El
340.It "Log File Handling"
341.Bl -tag -width 6n -compact
342.It Fn pmc_configure_logfile
343Configure a log file for
344.Xr hwpmc 4
345to write logged events to.
346.It Fn pmc_flush_logfile
347Flush all pending log data in
348.Xr hwpmc 4 Ns Ap s
349buffers.
350.It Fn pmc_close_logfile
351Flush all pending log data and close
352.Xr hwpmc 4 Ns Ap s
353side of the stream.
354.It Fn pmc_writelog
355Append arbitrary user data to the current log file.
356.El
357.It "PMC Management"
358.Bl -tag -width 6n -compact
359.It Fn pmc_allocate , Fn pmc_release
360Allocate (free) a PMC.
361.It Fn pmc_attach , Fn pmc_detach
362Attach (detach) a process scope PMC to a target.
363.It Fn pmc_read , Fn pmc_write , Fn pmc_rw
364Read (write) a value from (to) a PMC.
365.It Fn pmc_start , Fn pmc_stop
366Start (stop) a software PMC.
367.It Fn pmc_set
368Set the reload value for a sampling PMC.
369.El
370.It "Queries"
371.Bl -tag -width 6n -compact
372.It Fn pmc_capabilities
373Retrieve the capabilities for a given PMC.
374.It Fn pmc_cpuinfo
375Retrieve information about the CPUs and PMC hardware present in the
376system.
377.It Fn pmc_get_driver_stats
378Retrieve statistics maintained by
379.Xr hwpmc 4 .
380.It Fn pmc_ncpu
381Determine the greatest possible CPU number on the system.
382.It Fn pmc_npmc
383Return the number of hardware PMCs present in a given CPU.
384.It Fn pmc_pmcinfo
385Return information about the state of a given CPU's PMCs.
386.It Fn pmc_width
387Determine the width of a hardware counter in bits.
388.El
389.It "x86 Architecture Specific API"
390.Bl -tag -width 6n -compact
391.It Fn pmc_get_msr
392Returns the processor model specific register number
393associated with
394.Fa pmc .
395Applications may then use the x86
396.Ic RDPMC
397instruction to directly read the contents of the PMC.
398.El
399.El
400.Ss Signal Handling Requirements
401Applications using PMCs are required to handle the following signals:
402.Bl -tag -width ".Dv SIGBUS"
403.It Dv SIGBUS
404When the
405.Xr hwpmc 4
406module is unloaded using
407.Xr kldunload 8 ,
408processes that have PMCs allocated to them will be sent a
409.Dv SIGBUS
410signal.
411.It Dv SIGIO
412The
413.Xr hwpmc 4
414driver will send a PMC owning process a
415.Dv SIGIO
416signal if:
417.Bl -bullet
418.It
419any process-mode PMC allocated by it loses all its
420target processes.
421.It
422the driver encounters an error when writing log data to a
423configured log file.
424This error may be retrieved by a subsequent call to
425.Fn pmc_flush_logfile .
426.El
427.El
428.Ss Typical Program Flow
429.Bl -enum
430.It
431An application would first invoke function
432.Fn pmc_init
433to allow the library to initialize itself.
434.It
435Signal handling would then be set up.
436.It
437Next the application would allocate the PMCs it desires using function
438.Fn pmc_allocate .
439.It
440Initial values for PMCs may be set using function
441.Fn pmc_set .
442.It
443If a log file is necessary for the PMCs to work, it would
444be configured using function
445.Fn pmc_configure_logfile .
446.It
447Process scope PMCs would then be attached to their target processes
448using function
449.Fn pmc_attach .
450.It
451The PMCs would then be started using function
452.Fn pmc_start .
453.It
454Once started, the values of counting PMCs may be read using function
455.Fn pmc_read .
456For PMCs that write events to the log file, this logged data would be
457read and parsed using the
458.Xr pmclog 3
459family of functions.
460.It
461PMCs are stopped using function
462.Fn pmc_stop ,
463and process scope PMCs are detached from their targets using
464function
465.Fn pmc_detach .
466.It
467Before the process exits, it may release its PMCs using function
468.Fn pmc_release .
469Any configured log file may be closed using function
470.Fn pmc_configure_logfile .
471.El
472.Sh EVENT SPECIFIERS
473Event specifiers are strings comprising of an event name, followed by
474optional parameters modifying the semantics of the hardware event
475being probed.
476Event names are PMC architecture dependent, but the PMC library defines
477machine independent aliases for commonly used events.
478.Pp
479Event specifiers spellings are case-insensitive and space characters,
480periods, underscores and hyphens are considered equivalent to each other.
481Thus the event specifiers
482.Qq "Example Event" ,
483.Qq "example-event" ,
484and
485.Qq "EXAMPLE_EVENT"
486are equivalent.
487.Ss PMC Architecture Dependent Events
488PMC architecture dependent event specifiers are described in the
489following manual pages:
490.Bl -column " PMC_CLASS_TSC " "MANUAL PAGE "
491.It Em "PMC Class"      Ta Em "Manual Page"
492.It Li PMC_CLASS_IAF    Ta Xr pmc.iaf 3
493.It Li PMC_CLASS_IAP    Ta Xr pmc.atom 3 , Xr pmc.core 3 , Xr pmc.core2 3
494.It Li PMC_CLASS_K8     Ta Xr pmc.amd 3
495.It Li PMC_CLASS_TSC    Ta Xr pmc.tsc 3
496.El
497.Ss Event Name Aliases
498Event name aliases are PMC-independent names for commonly used events.
499The following aliases are known to this version of the
500.Nm pmc
501library:
502.Bl -tag -width indent
503.It Li branches
504Measure the number of branches retired.
505.It Li branch-mispredicts
506Measure the number of retired branches that were mispredicted.
507.It Li cycles
508Measure processor cycles.
509This event is implemented using the processor's Time Stamp Counter
510register.
511.It Li dc-misses
512Measure the number of data cache misses.
513.It Li ic-misses
514Measure the number of instruction cache misses.
515.It Li instructions
516Measure the number of instructions retired.
517.It Li interrupts
518Measure the number of interrupts seen.
519.It Li unhalted-cycles
520Measure the number of cycles the processor is not in a halted
521or sleep state.
522.El
523.Sh COMPATIBILITY
524The interface between the
525.Nm pmc
526library and the
527.Xr hwpmc 4
528driver is intended to be private to the implementation and may
529change.
530In order to ease forward compatibility with future versions of the
531.Xr hwpmc 4
532driver, applications are urged to dynamically link with the
533.Nm pmc
534library.
535Doing otherwise is unsupported.
536.Sh SEE ALSO
537.Xr pmc.amd 3 ,
538.Xr pmc.atom 3 ,
539.Xr pmc.core 3 ,
540.Xr pmc.core2 3 ,
541.Xr pmc.haswell 3 ,
542.Xr pmc.haswelluc 3 ,
543.Xr pmc.haswellxeon 3 ,
544.Xr pmc.iaf 3 ,
545.Xr pmc.ivybridge 3 ,
546.Xr pmc.ivybridgexeon 3 ,
547.Xr pmc.sandybridge 3 ,
548.Xr pmc.sandybridgeuc 3 ,
549.Xr pmc.sandybridgexeon 3 ,
550.Xr pmc.soft 3 ,
551.Xr pmc.tsc 3 ,
552.Xr pmc.westmere 3 ,
553.Xr pmc.westmereuc 3 ,
554.Xr pmc_allocate 3 ,
555.Xr pmc_attach 3 ,
556.Xr pmc_capabilities 3 ,
557.Xr pmc_configure_logfile 3 ,
558.Xr pmc_disable 3 ,
559.Xr pmc_event_names_of_class 3 ,
560.Xr pmc_get_driver_stats 3 ,
561.Xr pmc_get_msr 3 ,
562.Xr pmc_init 3 ,
563.Xr pmc_name_of_capability 3 ,
564.Xr pmc_read 3 ,
565.Xr pmc_set 3 ,
566.Xr pmc_start 3 ,
567.Xr pmclog 3 ,
568.Xr hwpmc 4 ,
569.Xr pmccontrol 8 ,
570.Xr pmcstat 8
571.Sh HISTORY
572The
573.Nm pmc
574library first appeared in
575.Fx 6.0 .
576.Sh AUTHORS
577The
578.Lb libpmc
579library was written by
580.An Joseph Koshy Aq Mt jkoshy@FreeBSD.org .
581