Lines Matching full:pmc

83 Subsequent operations on the allocated PMC use this handle to denote
84 the specific PMC.
85 A process that has successfully allocated a PMC is termed an
91 The PMC is active only when a thread belonging
94 The PMC operates independently of processes and
115 Scope and operational mode are orthogonal; a PMC may thus be
125 Applications can read the value of the PMC anytime using the
135 operation prior to starting the PMC.
155 operation prior to starting the PMC.
175 Stopping and starting a PMC is permitted at any time the owner process
176 has a valid handle to the PMC.
180 Attaching a process to a PMC is done using the
183 An already attached PMC may be detached from its target process
189 operation on an as yet unattached PMC will cause it to be attached
192 a PMC to another target process:
207 operation the handle to the PMC will become invalid.
212 of an allocated PMC:
222 This modifier is valid only for a PMC being allocated in process-private
224 It signifies that the PMC will track hardware events for its
227 This modifier is valid only for a PMC being allocated in process-private
234 This modifier is valid only for a PMC being allocated in process-private
239 a PMC.
265 operation was attempted on a process-private PMC that does not have
272 .Ss PMC ROW DISPOSITIONS
273 A PMC row is defined as the set of PMC resources at the same hardware
276 target threads, allocation of a process scope PMC reserves all PMCs in
277 a PMC row for use only with process scope PMCs.
278 Accordingly a PMC row will be in one of the following dispositions:
296 .Xr pmc 3
299 .Xr pmc 3
349 Allocate and configure a PMC.
350 On successful allocation, a handle to the PMC (a 32 bit value)
353 Attach a process mode PMC to a target process.
354 The PMC will be active whenever a thread in the target process is
359 flag had been specified at PMC allocation time, then the PMC is
362 Detach a PMC from its target process.
364 Release a PMC.
366 Read and write a PMC.
372 Start a PMC.
374 Stop a PMC.
380 user process to read a PMC value without needing to invoke a
383 On such CPUs, the machine address associated with an allocated PMC is
390 the given PMC handle.
392 The PMC needs to be in process-private mode and allocated without the
399 user process to read a PMC value without needing to invoke a
402 The machine address associated with an allocated PMC is
409 the given PMC handle.
411 The PMC needs to be in process-private mode and allocated without the
449 The size of the spin mutex pool used by the PMC driver.
574 .It pmc
632 kern.hwpmc.debugflags="pmc=allocate,release md=allocate,release"
673 operation was requested on an active system mode PMC.
682 request writing a new value was issued on a PMC that was active.
686 request was issued on a PMC that was active.
699 operation was requested on a system-wide sampling PMC without a log
705 of this PMC.
709 An invalid PMC handle was specified.
738 An invalid PMC ID was passed in for a
742 A suitable PMC matching the parameters passed in to a
746 An invalid PMC mode was requested during a
758 request for a process-private PMC.
764 request for a system-wide PMC.
775 request for a process-private PMC was issued for an event that does
778 A PMC allocated for system-wide operation was specified with a
794 request was issued for a PMC not attached to the target process.
804 operation was requested for a PMC not in process-virtual mode, or
805 for a PMC that is not solely attached to its owner process, or for
806 a PMC that was allocated with flag
828 operation specified allocation of a system-wide PMC on an absent or
835 request was issued for a system-wide PMC that was allocated on a CPU
840 request was issued for PMC capabilities not supported
841 by the specified PMC class.
844 A sampling mode PMC was requested on a CPU lacking an APIC.
859 operation was issued on a PMC whose MSR has been retrieved using
862 A process issued a PMC operation request without having allocated any
865 A process issued a PMC operation request after the PMC was detached
881 .Xr pmc 3 ,
942 This will ensure that an unprivileged process cannot attach a PMC