xref: /freebsd/lib/libpmc/pmc.3 (revision b6e28991bf3aadb74c54c7e6dfc2992b29abae5a)
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.\"
12026dbd29SChristian Brueffer.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
13026dbd29SChristian Brueffer.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
14026dbd29SChristian Brueffer.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
15026dbd29SChristian Brueffer.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
16026dbd29SChristian Brueffer.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
17026dbd29SChristian Brueffer.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
18026dbd29SChristian Brueffer.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
19026dbd29SChristian Brueffer.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
20026dbd29SChristian Brueffer.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
21026dbd29SChristian Brueffer.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
22026dbd29SChristian Brueffer.\" SUCH DAMAGE.
23ebccf1e3SJoseph Koshy.\"
24ebccf1e3SJoseph Koshy.\" $FreeBSD$
25ebccf1e3SJoseph Koshy.\"
26*b6e28991SAleksandr Rybalko.Dd May 28, 2022
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:
1149ee2158bSJoel Dahl.Bl -bullet
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
1239ee2158bSJoel Dahl.Pp
124c89d1cf5SJoseph KoshyUp to one log file may be configured per owner process.
125c89d1cf5SJoseph KoshyEvents logged to a log file may be subsequently analyzed using the
126c89d1cf5SJoseph Koshy.Xr pmclog 3
127c89d1cf5SJoseph Koshyfamily of functions.
128c89d1cf5SJoseph Koshy.Ss Supported CPUs
129c89d1cf5SJoseph KoshyThe CPUs known to the PMC library are named by the
130c89d1cf5SJoseph Koshy.Vt "enum pmc_cputype"
131c89d1cf5SJoseph Koshyenumeration.
132c89d1cf5SJoseph KoshySupported CPUs include:
1339ee2158bSJoel Dahl.Pp
13480f30b73SJoseph Koshy.Bl -tag -width "Li PMC_CPU_INTEL_CORE2" -compact
13580f30b73SJoseph Koshy.It Li PMC_CPU_AMD_K7
136c89d1cf5SJoseph Koshy.Tn "AMD Athlon"
137c89d1cf5SJoseph KoshyCPUs.
13880f30b73SJoseph Koshy.It Li PMC_CPU_AMD_K8
139c89d1cf5SJoseph Koshy.Tn "AMD Athlon64"
140c89d1cf5SJoseph KoshyCPUs.
14180f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_ATOM
14280f30b73SJoseph Koshy.Tn Intel
14380f30b73SJoseph Koshy.Tn Atom
14480f30b73SJoseph KoshyCPUs and other CPUs conforming to version 3 of the
14580f30b73SJoseph Koshy.Tn Intel
14680f30b73SJoseph Koshyperformance measurement architecture.
14780f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_CORE
14880f30b73SJoseph Koshy.Tn Intel
14980f30b73SJoseph Koshy.Tn Core Solo
15080f30b73SJoseph Koshyand
15180f30b73SJoseph Koshy.Tn Core Duo
15280f30b73SJoseph KoshyCPUs, and other CPUs conforming to version 1 of the
15380f30b73SJoseph Koshy.Tn Intel
15480f30b73SJoseph Koshyperformance measurement architecture.
15580f30b73SJoseph Koshy.It Li PMC_CPU_INTEL_CORE2
15680f30b73SJoseph Koshy.Tn Intel
15780f30b73SJoseph Koshy.Tn "Core2 Solo" ,
15880f30b73SJoseph Koshy.Tn "Core2 Duo"
15980f30b73SJoseph Koshyand
16080f30b73SJoseph Koshy.Tn "Core2 Extreme"
16180f30b73SJoseph KoshyCPUs, and other CPUs conforming to version 2 of the
16280f30b73SJoseph Koshy.Tn Intel
16380f30b73SJoseph Koshyperformance measurement architecture.
164c89d1cf5SJoseph Koshy.El
165c89d1cf5SJoseph Koshy.Ss Supported PMCs
166c89d1cf5SJoseph KoshyPMC supported by this library are named by the
167c89d1cf5SJoseph Koshy.Vt enum pmc_class
168c89d1cf5SJoseph Koshyenumeration.
169c89d1cf5SJoseph KoshySupported PMC kinds include:
1709ee2158bSJoel Dahl.Pp
17172cf78b8SJoseph Koshy.Bl -tag -width "Li PMC_CLASS_IAF" -compact
17272cf78b8SJoseph Koshy.It Li PMC_CLASS_IAF
173f20a61ffSJoseph KoshyFixed function hardware counters presents in CPUs conforming to the
17480f30b73SJoseph Koshy.Tn Intel
17580f30b73SJoseph Koshyperformance measurement architecture version 2 and later.
17672cf78b8SJoseph Koshy.It Li PMC_CLASS_IAP
17772cf78b8SJoseph KoshyProgrammable hardware counters present in CPUs conforming to the
17872cf78b8SJoseph Koshy.Tn Intel
17972cf78b8SJoseph Koshyperformance measurement architecture version 1 and later.
18080f30b73SJoseph Koshy.It Li PMC_CLASS_K7
181c89d1cf5SJoseph KoshyProgrammable hardware counters present in
182c89d1cf5SJoseph Koshy.Tn "AMD Athlon"
183c89d1cf5SJoseph KoshyCPUs.
18480f30b73SJoseph Koshy.It Li PMC_CLASS_K8
185c89d1cf5SJoseph KoshyProgrammable hardware counters present in
186c89d1cf5SJoseph Koshy.Tn "AMD Athlon64"
187c89d1cf5SJoseph KoshyCPUs.
18880f30b73SJoseph Koshy.It Li PMC_CLASS_TSC
18924f2c3f3SJoseph KoshyThe timestamp counter on i386 and amd64 architecture CPUs.
190f5f9340bSFabien Thomas.It Li PMC_CLASS_SOFT
191f5f9340bSFabien ThomasSoftware events.
192c89d1cf5SJoseph Koshy.El
193c89d1cf5SJoseph Koshy.Ss PMC Capabilities
194c89d1cf5SJoseph KoshyCapabilities of performance monitoring hardware are denoted using
195c89d1cf5SJoseph Koshythe
196c89d1cf5SJoseph Koshy.Vt "enum pmc_caps"
197c89d1cf5SJoseph Koshyenumeration.
198c89d1cf5SJoseph KoshySupported capabilities include:
1999ee2158bSJoel Dahl.Pp
20080f30b73SJoseph Koshy.Bl -tag -width "Li PMC_CAP_INTERRUPT" -compact
20180f30b73SJoseph Koshy.It Li PMC_CAP_CASCADE
20280f30b73SJoseph KoshyThe ability to cascade counters.
203*b6e28991SAleksandr Rybalko.It Li PMC_CAP_DOMWIDE
204*b6e28991SAleksandr RybalkoSeparate counters tied to each NUMA domain.
20580f30b73SJoseph Koshy.It Li PMC_CAP_EDGE
206c89d1cf5SJoseph KoshyThe ability to count negated to asserted transitions of the hardware
207c89d1cf5SJoseph Koshyconditions being probed for.
20880f30b73SJoseph Koshy.It Li PMC_CAP_INTERRUPT
209c89d1cf5SJoseph KoshyThe ability to interrupt the CPU.
21080f30b73SJoseph Koshy.It Li PMC_CAP_INVERT
211c89d1cf5SJoseph KoshyThe ability to invert the sense of the hardware conditions being
212c89d1cf5SJoseph Koshymeasured.
213624f6965SJoseph Koshy.It Li PMC_CAP_PRECISE
214624f6965SJoseph KoshyThe ability to perform precise sampling.
21580f30b73SJoseph Koshy.It Li PMC_CAP_QUALIFIER
216c89d1cf5SJoseph KoshyThe hardware allows monitored to be further qualified in some
217c89d1cf5SJoseph Koshysystem dependent way.
218624f6965SJoseph Koshy.It Li PMC_CAP_READ
219624f6965SJoseph KoshyThe ability to read from performance counters.
22080f30b73SJoseph Koshy.It Li PMC_CAP_SYSTEM
221c89d1cf5SJoseph KoshyThe ability to restrict counting of hardware events to when the CPU is
222c89d1cf5SJoseph Koshyrunning privileged code.
223*b6e28991SAleksandr Rybalko.It Li PMC_CAP_SYSWIDE
224*b6e28991SAleksandr RybalkoA single counter aggregating events for the whole system.
22580f30b73SJoseph Koshy.It Li PMC_CAP_THRESHOLD
226c89d1cf5SJoseph KoshyThe ability to ignore simultaneous hardware events below a
227c89d1cf5SJoseph Koshyprogrammable threshold.
22880f30b73SJoseph Koshy.It Li PMC_CAP_USER
229c89d1cf5SJoseph KoshyThe ability to restrict counting of hardware events to those when the
230c89d1cf5SJoseph KoshyCPU is running unprivileged code.
23180f30b73SJoseph Koshy.It Li PMC_CAP_WRITE
2320f3866faSJoseph KoshyThe ability to write to performance counters.
233c89d1cf5SJoseph Koshy.El
2346455febbSJoseph Koshy.Ss CPU Naming Conventions
235dd1259daSJoseph KoshyCPUs are named using small integers from zero up to, but
2366455febbSJoseph Koshyexcluding, the value returned by function
2376455febbSJoseph Koshy.Fn pmc_ncpu .
2386455febbSJoseph KoshyOn platforms supporting sparsely numbered CPUs not all the numbers in
2396455febbSJoseph Koshythis range will denote valid CPUs.
2406455febbSJoseph KoshyOperations on non-existent CPUs will return an error.
2416455febbSJoseph Koshy.Ss Functional Grouping of the API
242c89d1cf5SJoseph KoshyThis section contains a brief overview of the available functionality
243c89d1cf5SJoseph Koshyin the PMC library.
244c89d1cf5SJoseph KoshyEach function listed here is described further in its own manual page.
2459ee2158bSJoel Dahl.Bl -tag -width 2n
246c89d1cf5SJoseph Koshy.It Administration
2479ee2158bSJoel Dahl.Bl -tag -width 6n -compact
248c89d1cf5SJoseph Koshy.It Fn pmc_disable , Fn pmc_enable
249c89d1cf5SJoseph KoshyAdministratively disable (enable) specific performance monitoring
250c89d1cf5SJoseph Koshycounter hardware.
251c89d1cf5SJoseph KoshyCounters that are disabled will not be available to applications to
252c89d1cf5SJoseph Koshyuse.
253c89d1cf5SJoseph Koshy.El
254c89d1cf5SJoseph Koshy.It "Convenience Functions"
2559ee2158bSJoel Dahl.Bl -tag -width 6n -compact
256c89d1cf5SJoseph Koshy.It Fn pmc_event_names_of_class
257c89d1cf5SJoseph KoshyReturns a list of event names supported by a given PMC type.
258c89d1cf5SJoseph Koshy.It Fn pmc_name_of_capability
259c89d1cf5SJoseph KoshyConvert a
260c89d1cf5SJoseph Koshy.Dv PMC_CAP_*
261c89d1cf5SJoseph Koshyflag to a human-readable string.
262c89d1cf5SJoseph Koshy.It Fn pmc_name_of_class
263c89d1cf5SJoseph KoshyConvert a
264c89d1cf5SJoseph Koshy.Dv PMC_CLASS_*
265c89d1cf5SJoseph Koshyconstant to a human-readable string.
266c89d1cf5SJoseph Koshy.It Fn pmc_name_of_cputype
267c89d1cf5SJoseph KoshyReturn a human-readable name for a CPU type.
268c89d1cf5SJoseph Koshy.It Fn pmc_name_of_disposition
269c89d1cf5SJoseph KoshyReturn a human-readable string describing a PMC's disposition.
270c89d1cf5SJoseph Koshy.It Fn pmc_name_of_event
271c89d1cf5SJoseph KoshyConvert a numeric event code to a human-readable string.
272c89d1cf5SJoseph Koshy.It Fn pmc_name_of_mode
273c89d1cf5SJoseph KoshyConvert a
274c89d1cf5SJoseph Koshy.Dv PMC_MODE_*
275c89d1cf5SJoseph Koshyconstant to a human-readable name.
276c89d1cf5SJoseph Koshy.It Fn pmc_name_of_state
277c89d1cf5SJoseph KoshyReturn a human-readable string describing a PMC's current state.
278c89d1cf5SJoseph Koshy.El
279c89d1cf5SJoseph Koshy.It "Library Initialization"
2809ee2158bSJoel Dahl.Bl -tag -width 6n -compact
281c89d1cf5SJoseph Koshy.It Fn pmc_init
282c89d1cf5SJoseph KoshyInitialize the library.
283c89d1cf5SJoseph KoshyThis function must be called before any other library function.
284c89d1cf5SJoseph Koshy.El
285c89d1cf5SJoseph Koshy.It "Log File Handling"
2869ee2158bSJoel Dahl.Bl -tag -width 6n -compact
287c89d1cf5SJoseph Koshy.It Fn pmc_configure_logfile
288c89d1cf5SJoseph KoshyConfigure a log file for
289c89d1cf5SJoseph Koshy.Xr hwpmc 4
290c89d1cf5SJoseph Koshyto write logged events to.
291c89d1cf5SJoseph Koshy.It Fn pmc_flush_logfile
292c89d1cf5SJoseph KoshyFlush all pending log data in
293c89d1cf5SJoseph Koshy.Xr hwpmc 4 Ns Ap s
294c89d1cf5SJoseph Koshybuffers.
295dceed24aSFabien Thomas.It Fn pmc_close_logfile
296dceed24aSFabien ThomasFlush all pending log data and close
297dceed24aSFabien Thomas.Xr hwpmc 4 Ns Ap s
298dceed24aSFabien Thomasside of the stream.
299c89d1cf5SJoseph Koshy.It Fn pmc_writelog
300c89d1cf5SJoseph KoshyAppend arbitrary user data to the current log file.
301c89d1cf5SJoseph Koshy.El
302c89d1cf5SJoseph Koshy.It "PMC Management"
3039ee2158bSJoel Dahl.Bl -tag -width 6n -compact
304c89d1cf5SJoseph Koshy.It Fn pmc_allocate , Fn pmc_release
305c89d1cf5SJoseph KoshyAllocate (free) a PMC.
306c89d1cf5SJoseph Koshy.It Fn pmc_attach , Fn pmc_detach
307c89d1cf5SJoseph KoshyAttach (detach) a process scope PMC to a target.
308c89d1cf5SJoseph Koshy.It Fn pmc_read , Fn pmc_write , Fn pmc_rw
309c89d1cf5SJoseph KoshyRead (write) a value from (to) a PMC.
310c89d1cf5SJoseph Koshy.It Fn pmc_start , Fn pmc_stop
311c89d1cf5SJoseph KoshyStart (stop) a software PMC.
312c89d1cf5SJoseph Koshy.It Fn pmc_set
313c89d1cf5SJoseph KoshySet the reload value for a sampling PMC.
314c89d1cf5SJoseph Koshy.El
315c89d1cf5SJoseph Koshy.It "Queries"
3169ee2158bSJoel Dahl.Bl -tag -width 6n -compact
317c89d1cf5SJoseph Koshy.It Fn pmc_capabilities
318c89d1cf5SJoseph KoshyRetrieve the capabilities for a given PMC.
319c89d1cf5SJoseph Koshy.It Fn pmc_cpuinfo
320c89d1cf5SJoseph KoshyRetrieve information about the CPUs and PMC hardware present in the
321c89d1cf5SJoseph Koshysystem.
322c89d1cf5SJoseph Koshy.It Fn pmc_get_driver_stats
323c89d1cf5SJoseph KoshyRetrieve statistics maintained by
324c89d1cf5SJoseph Koshy.Xr hwpmc 4 .
325c89d1cf5SJoseph Koshy.It Fn pmc_ncpu
3266455febbSJoseph KoshyDetermine the greatest possible CPU number on the system.
327c89d1cf5SJoseph Koshy.It Fn pmc_npmc
328c89d1cf5SJoseph KoshyReturn the number of hardware PMCs present in a given CPU.
329c89d1cf5SJoseph Koshy.It Fn pmc_pmcinfo
330c89d1cf5SJoseph KoshyReturn information about the state of a given CPU's PMCs.
331c89d1cf5SJoseph Koshy.It Fn pmc_width
332c89d1cf5SJoseph KoshyDetermine the width of a hardware counter in bits.
333c89d1cf5SJoseph Koshy.El
334c89d1cf5SJoseph Koshy.It "x86 Architecture Specific API"
3359ee2158bSJoel Dahl.Bl -tag -width 6n -compact
336c89d1cf5SJoseph Koshy.It Fn pmc_get_msr
337c89d1cf5SJoseph KoshyReturns the processor model specific register number
338c89d1cf5SJoseph Koshyassociated with
339c5153e19SJoseph Koshy.Fa pmc .
340c89d1cf5SJoseph KoshyApplications may then use the x86
341c89d1cf5SJoseph Koshy.Ic RDPMC
342c89d1cf5SJoseph Koshyinstruction to directly read the contents of the PMC.
343c89d1cf5SJoseph Koshy.El
344c89d1cf5SJoseph Koshy.El
3459abe909bSRuslan Ermilov.Ss Signal Handling Requirements
346ebccf1e3SJoseph KoshyApplications using PMCs are required to handle the following signals:
347c89d1cf5SJoseph Koshy.Bl -tag -width ".Dv SIGBUS"
3489abe909bSRuslan Ermilov.It Dv SIGBUS
349ebccf1e3SJoseph KoshyWhen the
350ebccf1e3SJoseph Koshy.Xr hwpmc 4
351ebccf1e3SJoseph Koshymodule is unloaded using
352ebccf1e3SJoseph Koshy.Xr kldunload 8 ,
353ebccf1e3SJoseph Koshyprocesses that have PMCs allocated to them will be sent a
3549abe909bSRuslan Ermilov.Dv SIGBUS
3559abe909bSRuslan Ermilovsignal.
3569abe909bSRuslan Ermilov.It Dv SIGIO
357f263522aSJoseph KoshyThe
358f263522aSJoseph Koshy.Xr hwpmc 4
3599abe909bSRuslan Ermilovdriver will send a PMC owning process a
3609abe909bSRuslan Ermilov.Dv SIGIO
3619abe909bSRuslan Ermilovsignal if:
362f263522aSJoseph Koshy.Bl -bullet
363f263522aSJoseph Koshy.It
364f263522aSJoseph KoshyIf any process-mode PMC allocated by it loses all its
365f263522aSJoseph Koshytarget processes.
366f263522aSJoseph Koshy.It
367f263522aSJoseph KoshyIf the driver encounters an error when writing log data to a
368f263522aSJoseph Koshyconfigured log file.
369f263522aSJoseph KoshyThis error may be retrieved by a subsequent call to
370f263522aSJoseph Koshy.Fn pmc_flush_logfile .
371f263522aSJoseph Koshy.El
372ebccf1e3SJoseph Koshy.El
373c89d1cf5SJoseph Koshy.Ss Typical Program Flow
374c89d1cf5SJoseph Koshy.Bl -enum
375c89d1cf5SJoseph Koshy.It
376c89d1cf5SJoseph KoshyAn application would first invoke function
377c89d1cf5SJoseph Koshy.Fn pmc_init
378c89d1cf5SJoseph Koshyto allow the library to initialize itself.
379c89d1cf5SJoseph Koshy.It
380c89d1cf5SJoseph KoshySignal handling would then be set up.
381c89d1cf5SJoseph Koshy.It
382c89d1cf5SJoseph KoshyNext the application would allocate the PMCs it desires using function
383c89d1cf5SJoseph Koshy.Fn pmc_allocate .
384c89d1cf5SJoseph Koshy.It
385c89d1cf5SJoseph KoshyInitial values for PMCs may be set using function
386c89d1cf5SJoseph Koshy.Fn pmc_set .
387c89d1cf5SJoseph Koshy.It
388c89d1cf5SJoseph KoshyIf a log file is necessary for the PMCs to work, it would
389c89d1cf5SJoseph Koshybe configured using function
390c89d1cf5SJoseph Koshy.Fn pmc_configure_logfile .
391c89d1cf5SJoseph Koshy.It
392c89d1cf5SJoseph KoshyProcess scope PMCs would then be attached to their target processes
393c89d1cf5SJoseph Koshyusing function
394c89d1cf5SJoseph Koshy.Fn pmc_attach .
395c89d1cf5SJoseph Koshy.It
396c89d1cf5SJoseph KoshyThe PMCs would then be started using function
397c89d1cf5SJoseph Koshy.Fn pmc_start .
398c89d1cf5SJoseph Koshy.It
399c89d1cf5SJoseph KoshyOnce started, the values of counting PMCs may be read using function
400b53a052dSJoseph Koshy.Fn pmc_read .
401c89d1cf5SJoseph KoshyFor PMCs that write events to the log file, this logged data would be
402c89d1cf5SJoseph Koshyread and parsed using the
403c89d1cf5SJoseph Koshy.Xr pmclog 3
404c89d1cf5SJoseph Koshyfamily of functions.
405c89d1cf5SJoseph Koshy.It
406c89d1cf5SJoseph KoshyPMCs are stopped using function
407c89d1cf5SJoseph Koshy.Fn pmc_stop ,
408c89d1cf5SJoseph Koshyand process scope PMCs are detached from their targets using
409c89d1cf5SJoseph Koshyfunction
410c89d1cf5SJoseph Koshy.Fn pmc_detach .
411c89d1cf5SJoseph Koshy.It
412c89d1cf5SJoseph KoshyBefore the process exits, its may release its PMCs using function
413c89d1cf5SJoseph Koshy.Fn pmc_release .
414c89d1cf5SJoseph KoshyAny configured log file may be closed using function
415c89d1cf5SJoseph Koshy.Fn pmc_configure_logfile .
416c89d1cf5SJoseph Koshy.El
417ebccf1e3SJoseph Koshy.Sh EVENT SPECIFIERS
418ebccf1e3SJoseph KoshyEvent specifiers are strings comprising of an event name, followed by
419ebccf1e3SJoseph Koshyoptional parameters modifying the semantics of the hardware event
420ebccf1e3SJoseph Koshybeing probed.
4210b844226SJoseph KoshyEvent names are PMC architecture dependent, but the PMC library defines
4220b844226SJoseph Koshymachine independent aliases for commonly used events.
4230f7668cbSJoseph Koshy.Pp
4240f7668cbSJoseph KoshyEvent specifiers spellings are case-insensitive and space characters,
4250f7668cbSJoseph Koshyperiods, underscores and hyphens are considered equivalent to each other.
4260f7668cbSJoseph KoshyThus the event specifiers
4270f7668cbSJoseph Koshy.Qq "Example Event" ,
4280f7668cbSJoseph Koshy.Qq "example-event" ,
4290f7668cbSJoseph Koshyand
4300f7668cbSJoseph Koshy.Qq "EXAMPLE_EVENT"
4310f7668cbSJoseph Koshyare equivalent.
4320f7668cbSJoseph Koshy.Ss PMC Architecture Dependent Events
4330f7668cbSJoseph KoshyPMC architecture dependent event specifiers are described in the
4340f7668cbSJoseph Koshyfollowing manual pages:
4350f7668cbSJoseph Koshy.Bl -column " PMC_CLASS_TSC " "MANUAL PAGE "
4360f7668cbSJoseph Koshy.It Em "PMC Class"      Ta Em "Manual Page"
4370f7668cbSJoseph Koshy.It Li PMC_CLASS_IAF    Ta Xr pmc.iaf 3
4380f7668cbSJoseph Koshy.It Li PMC_CLASS_IAP    Ta Xr pmc.atom 3 , Xr pmc.core 3 , Xr pmc.core2 3
4390f7668cbSJoseph Koshy.It Li PMC_CLASS_K7     Ta Xr pmc.k7 3
4400f7668cbSJoseph Koshy.It Li PMC_CLASS_K8     Ta Xr pmc.k8 3
4410f7668cbSJoseph Koshy.It Li PMC_CLASS_TSC    Ta Xr pmc.tsc 3
4420f7668cbSJoseph Koshy.El
443ebccf1e3SJoseph Koshy.Ss Event Name Aliases
44424f2c3f3SJoseph KoshyEvent name aliases are PMC-independent names for commonly used events.
445ebccf1e3SJoseph KoshyThe following aliases are known to this version of the
446110e1704SRuslan Ermilov.Nm pmc
447ebccf1e3SJoseph Koshylibrary:
448ebccf1e3SJoseph Koshy.Bl -tag -width indent
449ebccf1e3SJoseph Koshy.It Li branches
450ebccf1e3SJoseph KoshyMeasure the number of branches retired.
451ebccf1e3SJoseph Koshy.It Li branch-mispredicts
452ebccf1e3SJoseph KoshyMeasure the number of retired branches that were mispredicted.
453ebccf1e3SJoseph Koshy.It Li cycles
454ebccf1e3SJoseph KoshyMeasure processor cycles.
455ebccf1e3SJoseph KoshyThis event is implemented using the processor's Time Stamp Counter
456ebccf1e3SJoseph Koshyregister.
457ebccf1e3SJoseph Koshy.It Li dc-misses
458ebccf1e3SJoseph KoshyMeasure the number of data cache misses.
459ebccf1e3SJoseph Koshy.It Li ic-misses
460ebccf1e3SJoseph KoshyMeasure the number of instruction cache misses.
461ebccf1e3SJoseph Koshy.It Li instructions
462ebccf1e3SJoseph KoshyMeasure the number of instructions retired.
463ebccf1e3SJoseph Koshy.It Li interrupts
464ebccf1e3SJoseph KoshyMeasure the number of interrupts seen.
465177a2f22SJoseph Koshy.It Li unhalted-cycles
466177a2f22SJoseph KoshyMeasure the number of cycles the processor is not in a halted
467177a2f22SJoseph Koshyor sleep state.
468ebccf1e3SJoseph Koshy.El
4695138c36aSJoseph Koshy.Sh COMPATIBILITY
4705138c36aSJoseph KoshyThe interface between the
471110e1704SRuslan Ermilov.Nm pmc
4725138c36aSJoseph Koshylibrary and the
4735138c36aSJoseph Koshy.Xr hwpmc 4
4745138c36aSJoseph Koshydriver is intended to be private to the implementation and may
4755138c36aSJoseph Koshychange.
4765138c36aSJoseph KoshyIn order to ease forward compatibility with future versions of the
4775138c36aSJoseph Koshy.Xr hwpmc 4
4785138c36aSJoseph Koshydriver, applications are urged to dynamically link with the
479110e1704SRuslan Ermilov.Nm pmc
4805138c36aSJoseph Koshylibrary.
4815138c36aSJoseph Koshy.Pp
4825138c36aSJoseph KoshyThe
483110e1704SRuslan Ermilov.Nm pmc
4845138c36aSJoseph KoshyAPI is
4855138c36aSJoseph Koshy.Ud
486ebccf1e3SJoseph Koshy.Sh SEE ALSO
48772cf78b8SJoseph Koshy.Xr pmc.atom 3 ,
48872cf78b8SJoseph Koshy.Xr pmc.core 3 ,
48972cf78b8SJoseph Koshy.Xr pmc.core2 3 ,
49056e39702SGeorge V. Neville-Neil.Xr pmc.haswell 3 ,
49156e39702SGeorge V. Neville-Neil.Xr pmc.haswelluc 3 ,
492f1ec0939SRyan Stone.Xr pmc.haswellxeon 3 ,
49372cf78b8SJoseph Koshy.Xr pmc.iaf 3 ,
49456e39702SGeorge V. Neville-Neil.Xr pmc.ivybridge 3 ,
49556e39702SGeorge V. Neville-Neil.Xr pmc.ivybridgexeon 3 ,
49624f2c3f3SJoseph Koshy.Xr pmc.k7 3 ,
49724f2c3f3SJoseph Koshy.Xr pmc.k8 3 ,
49856e39702SGeorge V. Neville-Neil.Xr pmc.sandybridge 3 ,
49956e39702SGeorge V. Neville-Neil.Xr pmc.sandybridgeuc 3 ,
50056e39702SGeorge V. Neville-Neil.Xr pmc.sandybridgexeon 3 ,
501f5f9340bSFabien Thomas.Xr pmc.soft 3 ,
50224f2c3f3SJoseph Koshy.Xr pmc.tsc 3 ,
50356e39702SGeorge V. Neville-Neil.Xr pmc.westmere 3 ,
50456e39702SGeorge V. Neville-Neil.Xr pmc.westmereuc 3 ,
5057a40330bSEnji Cooper.Xr pmc_allocate 3 ,
5067a40330bSEnji Cooper.Xr pmc_attach 3 ,
5077a40330bSEnji Cooper.Xr pmc_capabilities 3 ,
5087a40330bSEnji Cooper.Xr pmc_configure_logfile 3 ,
5097a40330bSEnji Cooper.Xr pmc_disable 3 ,
5107a40330bSEnji Cooper.Xr pmc_event_names_of_class 3 ,
5117a40330bSEnji Cooper.Xr pmc_get_driver_stats 3 ,
5127a40330bSEnji Cooper.Xr pmc_get_msr 3 ,
5137a40330bSEnji Cooper.Xr pmc_init 3 ,
5147a40330bSEnji Cooper.Xr pmc_name_of_capability 3 ,
5157a40330bSEnji Cooper.Xr pmc_read 3 ,
5167a40330bSEnji Cooper.Xr pmc_set 3 ,
5177a40330bSEnji Cooper.Xr pmc_start 3 ,
518f263522aSJoseph Koshy.Xr pmclog 3 ,
519ebccf1e3SJoseph Koshy.Xr hwpmc 4 ,
520ebccf1e3SJoseph Koshy.Xr pmccontrol 8 ,
521ebccf1e3SJoseph Koshy.Xr pmcstat 8
5225138c36aSJoseph Koshy.Sh HISTORY
5235138c36aSJoseph KoshyThe
524110e1704SRuslan Ermilov.Nm pmc
5255138c36aSJoseph Koshylibrary first appeared in
5265138c36aSJoseph Koshy.Fx 6.0 .
527c89d1cf5SJoseph Koshy.Sh AUTHORS
528c89d1cf5SJoseph KoshyThe
529c89d1cf5SJoseph Koshy.Lb libpmc
530c89d1cf5SJoseph Koshylibrary was written by
5312b7af31cSBaptiste Daroussin.An Joseph Koshy Aq Mt jkoshy@FreeBSD.org .
532