Lines Matching full:thread

32 .Fn sched:::change-pri "struct thread *" "struct proc *" "uint8_t"
33 .Fn sched:::dequeue "struct thread *" "struct proc *" "void *"
34 .Fn sched:::enqueue "struct thread *" "struct proc *" "void *" "int"
35 .Fn sched:::lend-pri "struct thread *" "struct proc *" "uint8_t" "struct thread *"
37 .Fn sched:::off-cpu "struct thread *" "struct proc *"
41 .Fn sched:::surrender "struct thread *" "struct proc *"
43 .Fn sched:::tick "struct thread *" "struct proc *"
44 .Fn sched:::wakeup "struct thread *" "struct proc *"
53 probe fires when a thread's active scheduling priority is about to be updated.
54 The first two arguments are the thread whose priority is about to be changed,
56 The third argument is the new absolute priority for the thread, while the
61 probe fires when the currently-running thread elevates the priority of another
62 thread via priority lending.
63 The first two arguments are the thread whose priority is about to be changed,
65 The third argument is the new absolute priority for the thread.
66 The fourth argument is the currently-running thread.
70 probe fires immediately before a runnable thread is removed from a scheduler
72 This may occur when the thread is about to begin execution on a CPU, or because
73 the thread is being migrated to a different run queue.
75 attempting to rebalance load between multiple CPUs, the thread's scheduling
76 priority may have changed, or the thread's CPU affinity settings may have
80 are the thread and corresponding process.
85 probe fires when a runnable thread is about to be added to a scheduler run
87 Its first two arguments are the thread and corresponding process.
90 The fourth argument is a boolean value that is non-zero if the thread is
91 enqueued at the beginning of its run queue slot, and zero if the thread is
96 probe fires after the load of a thread queue is adjusted.
97 The first argument is the cpuid for the CPU associated with the thread queue,
98 and the second argument is the adjusted load of the thread queue, i.e., the
104 currently-running thread, and the
106 probe fires when the current thread has been selected to run on a CPU and is
110 are the thread and corresponding process selected to run following the
111 currently-running thread.
119 a thread running on a different CPU, via an interprocessor interrupt.
120 The arguments to this probe are the interrupted thread and its corresponding
122 This probe currently always fires in the context of the interrupted thread.
126 probe will fire immediately before the currently-running thread is preempted.
127 When this occurs, the scheduler will select a new thread to run, and one of the
132 the preempted thread.
136 probe fires immediately before the currently-running thread is about to suspend
140 probe fires when a thread is set up to resume execution after having gone to
142 Its arguments are the thread being awoken, and the corresponding process.
147 Its arguments are the currently-running thread and its corresponding process.
154 .Vt "struct thread"
158 In a probe body, the currently-running thread can always be obtained with the
161 .Vt "struct thread *" .
162 For example, when a running thread is about to sleep, the
164 probe fires in the context of that thread, which can be accessed using
169 thread is executing.
186 Here, DTrace stores a timestamp each time a thread is scheduled to run, and