| /Linux-v5.15/include/trace/events/ |
| D | irq.h | 103 DECLARE_EVENT_CLASS(softirq,
128 DEFINE_EVENT(softirq, softirq_entry,
142 DEFINE_EVENT(softirq, softirq_exit,
156 DEFINE_EVENT(softirq, softirq_raise,
|
| /Linux-v5.15/fs/proc/ |
| D | stat.c | 111 u64 user, nice, system, idle, iowait, irq, softirq, steal; in show_stat() local
119 irq = softirq = steal = 0; in show_stat()
137 softirq += cpustat[CPUTIME_SOFTIRQ]; in show_stat()
159 seq_put_decimal_ull(p, " ", nsec_to_clock_t(softirq)); in show_stat()
178 softirq = cpustat[CPUTIME_SOFTIRQ]; in show_stat()
189 seq_put_decimal_ull(p, " ", nsec_to_clock_t(softirq)); in show_stat()
|
| /Linux-v5.15/kernel/trace/ |
| D | trace_osnoise.c | 100 struct osn_softirq softirq; member
528 if (osn_var->softirq.delta_start) in cond_move_softirq_delta_start()
529 osn_var->softirq.delta_start += duration; in cond_move_softirq_delta_start()
848 osn_var->softirq.arrival_time = time_get(); in trace_softirq_entry_callback()
849 set_int_safe_time(osn_var, &osn_var->softirq.delta_start); in trace_softirq_entry_callback()
850 osn_var->softirq.count++; in trace_softirq_entry_callback()
878 osn_var->softirq.arrival_time = 0; in trace_softirq_exit_callback()
879 osn_var->softirq.delta_start = 0; in trace_softirq_exit_callback()
885 duration = get_int_safe_duration(osn_var, &osn_var->softirq.delta_start); in trace_softirq_exit_callback()
886 trace_softirq_noise(vec_nr, osn_var->softirq.arrival_time, duration); in trace_softirq_exit_callback()
[all …]
|
| D | trace_output.c | 456 int softirq; in trace_print_lat_fmt() local
461 softirq = entry->flags & TRACE_FLAG_SOFTIRQ; in trace_print_lat_fmt()
487 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
489 softirq ? 's' : in trace_print_lat_fmt()
|
| /Linux-v5.15/arch/s390/kernel/ |
| D | vtime.c | 127 u64 timer, clock, user, guest, system, hardirq, softirq; in do_account_vtime() local
160 softirq = update_tsk_timer(&tsk->thread.softirq_timer, in do_account_vtime()
163 clock - user - guest - system - hardirq - softirq; in do_account_vtime()
180 if (softirq) in do_account_vtime()
181 account_system_index_scaled(tsk, softirq, CPUTIME_SOFTIRQ); in do_account_vtime()
183 return virt_timer_forward(user + guest + system + hardirq + softirq); in do_account_vtime()
|
| /Linux-v5.15/Documentation/RCU/ |
| D | UP.rst | 15 Example 1: softirq Suicide
20 this same list in softirq context. Suppose that the process-context scan
21 is referencing element B when it is interrupted by softirq processing,
26 from softirq, the list scan would find itself referencing a newly freed
125 then, since RCU callbacks can be invoked from softirq context,
126 the callback might be called from a softirq that interrupted
|
| D | stallwarn.rst | 57 is running at a higher priority than the RCU softirq threads.
73 prevent RCU's kthreads and softirq handlers from running.
196 2-...: (3 GPs behind) idle=06c/0/0 softirq=1453/1455 fqs=0
197 16-...: (0 ticks this GP) idle=81c/0/0 softirq=764/764 fqs=0
223 The "softirq=" portion of the message tracks the number of RCU softirq
231 across repeated stall-warning messages, it is possible that RCU's softirq
234 kernels, if a high-priority process is starving RCU's softirq handler.
250 …0: (64628 ticks this GP) idle=dd5/3fffffffffffffff/0 softirq=82/543 last_accelerate: a345/d342 dyn…
311 Possible timer handling issue on cpu=4 timer-softirq=11142
314 where it queued the fqs timer. The number following the "timer-softirq"
|
| D | checklist.rst | 188 be called from softirq context. In particular, it cannot block.
219 and re-enables softirq, for example, rcu_read_lock_bh() and
242 network-driver NAPI (softirq) context. BPF relies heavily on RCU
342 with softirq disabled, e.g., via spin_lock_irqsave(),
343 spin_lock_bh(), etc. Failing to disable softirq on a given
345 the RCU softirq handler happens to run your RCU callback while
|
| /Linux-v5.15/Documentation/translations/it_IT/kernel-hacking/ |
| D | locking.rst | 178 Sincronizzazione fra il contesto utente e i softirq
181 Se un softirq condivide dati col contesto utente, avete due problemi.
182 Primo, il contesto utente corrente potrebbe essere interroto da un softirq,
185 (``include/linux/spinlock.h``) viene utilizzato. Questo disabilita i softirq
197 (``include/linux/interrupt.h``), la quale impedisce ai softirq d'essere
203 Questo caso è uguale al precedente, un tasklet viene eseguito da un softirq.
209 softirq.
234 Sincronizzazione fra softirq
237 Spesso un softirq potrebbe condividere dati con se stesso o un tasklet/timer.
239 Lo stesso softirq argument
[all …]
|
| D | hacking.rst | 40 - non associata ad alcun processo, servendo un softirq o tasklet;
50 softirq è in esecuzione su d'una CPU, nessun altro softirq può avvicendarsi
77 Attenzione che se avete la prelazione o i softirq disabilitati (vedere
101 Contesto d'interruzione software: softirq e tasklet
107 eseguita (``kernel/softirq.c``).
116 Il file ``include/linux/interrupt.h`` elenca i differenti tipi di 'softirq'.
117 Un tipo di softirq molto importante è il timer (``include/linux/timer.h``):
121 Dato che i softirq possono essere eseguiti simultaneamente su più di un
135 Potete determinate se siete in un softirq (o tasklet) utilizzando la
433 Lo scopo è di prevenire l'esecuzione di softirq e tasklet sul processore
|
| /Linux-v5.15/Documentation/locking/ |
| D | lockdep-design.rst | 55 - softirq
88 ||| \-> softirq disabled and not in softirq context
89 || \--> acquired in softirq context
120 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The
125 <softirq-safe> or <softirq-unsafe>
160 <softirq-safe> -> <softirq-unsafe>
164 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
165 lock could be taken by an softirq context, interrupting a softirq-unsafe
178 - if a new softirq-safe lock is discovered, we check whether it took
179 any softirq-unsafe lock in the past.
[all …]
|
| D | seqlock.rst | 49 softirq contexts, interrupts or bottom halves must also be respectively
167 If the read side section can be invoked from hardirq or softirq context,
|
| /Linux-v5.15/Documentation/kernel-hacking/ |
| D | locking.rst | 164 If a softirq shares data with user context, you have two problems.
165 Firstly, the current user context can be interrupted by a softirq, and
180 (``include/linux/interrupt.h``), which protects you from the softirq
187 from a softirq.
193 from a softirq. From a locking point of view, tasklets and timers are
221 Often a softirq might want to share data with itself or a tasklet/timer.
226 The same softirq can run on the other CPUs: you can use a per-CPU array
228 going so far as to use a softirq, you probably care about scalable
239 tasklet, different softirq or the same or another softirq: any of them
245 Hardware interrupts usually communicate with a tasklet or softirq.
[all …]
|
| D | hacking.rst | 32 - not associated with any process, serving a softirq or tasklet;
40 by the ones above it. For example, while a softirq is running on a CPU,
41 no other softirq will preempt it, but a hardware interrupt can. However,
92 pending (usually by hardware interrupts) are run (``kernel/softirq.c``).
101 important softirq is the timer softirq (``include/linux/timer.h``): you
105 Softirqs are often a pain to deal with, since the same softirq will run
118 You can tell you are in a softirq (or tasklet) using the
|
| /Linux-v5.15/Documentation/translations/zh_CN/core-api/irq/ |
| D | irqflags-tracing.rst | 17 “irq-flags tracing”（中断标志追踪）功能可以 “追踪” hardirq和softirq的状态，它让
|
| /Linux-v5.15/Documentation/translations/zh_CN/infiniband/ |
| D | core_locking.rst | 98 进程上下文、softirq上下文或中断上下文。上层协议使用者可能不会在回调中睡眠。
|
| /Linux-v5.15/Documentation/timers/ |
| D | highres.rst | 176 red-black tree to a separate double linked list and invokes the softirq
183 context to the softirq and to the task which is woken up by the expired
199 The softirq for running the hrtimer queues and executing the callbacks has been
200 separated from the tick bound timer softirq to allow accurate delivery of high
202 timers. The execution of this softirq can still be delayed by other softirqs,
|
| /Linux-v5.15/Documentation/scheduler/ |
| D | sched-domains.rst | 35 through scheduler_tick(). It raises a softirq after the next regularly scheduled
38 in softirq context (SCHED_SOFTIRQ).
|
| /Linux-v5.15/Documentation/trace/ |
| D | ftrace.rst | 854 # | / _---=> hardirq/softirq
907 # || / _---=> hardirq/softirq
965 hardirq/softirq:
968 - 'H' - hard irq occurred inside a softirq.
1379 # || / _---=> hardirq/softirq
1430 # || / _---=> hardirq/softirq
1507 # | / _---=> hardirq/softirq
1578 # || / _---=> hardirq/softirq
1616 # || / _---=> hardirq/softirq
1730 # || / _---=> hardirq/softirq
[all …]
|
| /Linux-v5.15/Documentation/vm/ |
| D | page_frags.rst | 34 only usable within the softirq context.
|
| /Linux-v5.15/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v5.15/Documentation/admin-guide/sysctl/ |
| D | net.rst | 139 of the driver for the per softirq cycle netdev_budget. This parameter influences
141 processing during RX softirq cycles. It is further meant for making current
151 Scales the maximum number of packets that can be processed during a TX softirq cycle.
153 net stack processing needs. Be careful to avoid making TX softirq processing a CPU hog.
|
| /Linux-v5.15/Documentation/networking/ |
| D | x25-iface.rst | 82 call "netif_receive_skb_core" from softirq context to deliver them.
|
| /Linux-v5.15/Documentation/translations/zh_CN/kernel-hacking/ |
| D | hacking.rst | 33 - 与任何进程无关，服务于软件中断（softirq）或子任务（tasklet）；
81 过硬件中断）的“软件中断”将运行（ ``kernel/softirq.c`` ）。
|
| /Linux-v5.15/kernel/ |
| D | Makefile | 7 cpu.o exit.o softirq.o resource.o \
|
