Lines Matching full:process
82 request will return a handle to the requesting process.
85 A process that has successfully allocated a PMC is termed an
86 .Dq "owner process" .
88 PMCs may be allocated with process or system scope.
89 .Bl -tag -width ".Em Process-scope"
90 .It Em "Process-scope"
92 to a process it is attached to is scheduled on a CPU.
118 .It Process-scope, counting
119 These PMCs count hardware events whenever a thread in their attached process is
128 .It Process-scope, sampling
132 process is active.
160 System-wide statistical sampling can only be enabled by a process with
166 Processes may mix allocations of system-wide and process-private
175 Stopping and starting a PMC is permitted at any time the owner process
178 Process-private PMCs need to be attached to a target process before
180 Attaching a process to a PMC is done using the
183 An already attached PMC may be detached from its target process
190 to its owner process.
191 The following rules determine whether a given process may attach
192 a PMC to another target process:
195 A non-jailed process with super-user privileges is allowed to attach
196 to any other process in the system.
222 This modifier is valid only for a PMC being allocated in process-private
225 target process and the target's current and future descendants.
227 This modifier is valid only for a PMC being allocated in process-private
232 seen by the target process when it was scheduled on the CPU.
234 This modifier is valid only for a PMC being allocated in process-private
238 will maintain per-process counts for each target process attached to
240 At process exit time, a record containing the target process' PID and
241 the accumulated per-process count for that process will be written to the
256 cannot be started until their owner process has configured a log file.
265 operation was attempted on a process-private PMC that does not have
275 Since process scope PMCs need to move between CPUs following their
276 target threads, allocation of a process scope PMC reserves all PMCs in
277 a PMC row for use only with process scope PMCs.
282 either of system scope or process scope allocation requests.
284 Hardware counters in this row are in use by process scope PMCs
285 and are only available for process scope allocation requests.
291 No process scope PMCs will use hardware counters in this row.
345 The invoking process needs to possess the
353 Attach a process mode PMC to a target process.
354 The PMC will be active whenever a thread in the target process is
360 attached to all current and future descendants of the target process.
362 Detach a PMC from its target process.
380 user process to read a PMC value without needing to invoke a
392 The PMC needs to be in process-private mode and allocated without the
394 modifier flag, and should be attached only to its owner process at the
399 user process to read a PMC value without needing to invoke a
411 The PMC needs to be in process-private mode and allocated without the
413 modifier flag, and should be attached only to its owner process at the
499 driver will reject allocation requests for process-private PMCs that
512 The module loading process failed because a version mismatch was detected
515 The module loading process failed because the currently executing kernel
576 .It process
577 Process events
635 To trace all events in the process and context switch major flag groups:
637 kern.hwpmc.debugflags="process=* csw=*"
658 Helper process creation failed for a
669 process-private PMCs.
677 operation was requested for a target process that already had another
704 request was reissued for a target process that already is the target
758 request for a process-private PMC.
775 request for a process-private PMC was issued for an event that does
790 request specified an illegal process ID.
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
811 request was issued for an owner process without a log file
848 request was issued by a process without super-user
849 privilege or by a jailed super-user process.
853 operation was issued for a target process that the current process
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
872 request specified a non-existent process ID.
874 The target process for a
942 This will ensure that an unprivileged process cannot attach a PMC
943 to any process other than itself and thus cannot observe the hardware