| /Linux-v5.4/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.4/fs/proc/ |
| D | stat.c | 110 u64 user, nice, system, idle, iowait, irq, softirq, steal; in show_stat() local
118 irq = softirq = steal = 0; in show_stat()
131 softirq += kcs->cpustat[CPUTIME_SOFTIRQ]; in show_stat()
153 seq_put_decimal_ull(p, " ", nsec_to_clock_t(softirq)); in show_stat()
169 softirq = kcs->cpustat[CPUTIME_SOFTIRQ]; in show_stat()
180 seq_put_decimal_ull(p, " ", nsec_to_clock_t(softirq)); in show_stat()
|
| /Linux-v5.4/arch/s390/kernel/ |
| D | vtime.c | 127 u64 timer, clock, user, guest, system, hardirq, softirq; in do_account_vtime() local
162 softirq = update_tsk_timer(&tsk->thread.softirq_timer, in do_account_vtime()
165 clock - user - guest - system - hardirq - softirq; in do_account_vtime()
182 if (softirq) in do_account_vtime()
183 account_system_index_scaled(tsk, softirq, CPUTIME_SOFTIRQ); in do_account_vtime()
185 return virt_timer_forward(user + guest + system + hardirq + softirq); in do_account_vtime()
|
| /Linux-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 53 - softirq
85 ||| \-> softirq disabled and not in softirq context
86 || \--> acquired in softirq context
117 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The
122 <softirq-safe> or <softirq-unsafe>
157 <softirq-safe> -> <softirq-unsafe>
161 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
162 lock could be taken by an softirq context, interrupting a softirq-unsafe
175 - if a new softirq-safe lock is discovered, we check whether it took
176 any softirq-unsafe lock in the past.
[all …]
|
| /Linux-v5.4/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.txt | 52 is running at a higher priority than the RCU softirq threads.
68 prevent RCU's kthreads and softirq handlers from running.
176 2-...: (3 GPs behind) idle=06c/0/0 softirq=1453/1455 fqs=0
177 16-...: (0 ticks this GP) idle=81c/0/0 softirq=764/764 fqs=0
201 The "softirq=" portion of the message tracks the number of RCU softirq
209 across repeated stall-warning messages, it is possible that RCU's softirq
212 kernels, if a high-priority process is starving RCU's softirq handler.
228 …0: (64628 ticks this GP) idle=dd5/3fffffffffffffff/0 softirq=82/543 last_accelerate: a345/d342 Non…
|
| D | checklist.txt | 186 be called from softirq context. In particular, it cannot block.
230 disabled, for example, in irq or softirq context. Commenting
320 with softirq disabled, e.g., via spin_lock_irqsave(),
321 spin_lock_bh(), etc. Failing to disable softirq on a given
323 the RCU softirq handler happens to run your RCU callback while
|
| /Linux-v5.4/Documentation/translations/it_IT/kernel-hacking/ |
| D | locking.rst | 176 Sincronizzazione fra il contesto utente e i softirq
179 Se un softirq condivide dati col contesto utente, avete due problemi.
180 Primo, il contesto utente corrente potrebbe essere interroto da un softirq,
183 (``include/linux/spinlock.h``) viene utilizzato. Questo disabilita i softirq
195 (``include/linux/interrupt.h``), la quale impedisce ai softirq d'essere
201 Questo caso è uguale al precedente, un tasklet viene eseguito da un softirq.
207 softirq.
232 Sincronizzazione fra softirq
235 Spesso un softirq potrebbe condividere dati con se stesso o un tasklet/timer.
237 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.4/Documentation/kernel-hacking/ |
| D | locking.rst | 170 If a softirq shares data with user context, you have two problems.
171 Firstly, the current user context can be interrupted by a softirq, and
186 (``include/linux/interrupt.h``), which protects you from the softirq
193 from a softirq.
199 from a softirq. From a locking point of view, tasklets and timers are
227 Often a softirq might want to share data with itself or a tasklet/timer.
232 The same softirq can run on the other CPUs: you can use a per-CPU array
234 going so far as to use a softirq, you probably care about scalable
245 tasklet, different softirq or the same or another softirq: any of them
251 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.4/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.4/block/ |
| D | Makefile | 8 blk-exec.o blk-merge.o blk-softirq.o blk-timeout.o \
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-domains.rst | 33 through scheduler_tick(). It raises a softirq after the next regularly scheduled
36 in softirq context (SCHED_SOFTIRQ).
|
| /Linux-v5.4/kernel/trace/ |
| D | trace_output.c | 431 int softirq; in trace_print_lat_fmt() local
436 softirq = entry->flags & TRACE_FLAG_SOFTIRQ; in trace_print_lat_fmt()
462 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
464 softirq ? 's' : in trace_print_lat_fmt()
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | net.rst | 138 of the driver for the per softirq cycle netdev_budget. This parameter influences
140 processing during RX softirq cycles. It is further meant for making current
150 Scales the maximum number of packets that can be processed during a TX softirq cycle.
152 net stack processing needs. Be careful to avoid making TX softirq processing a CPU hog.
|
| /Linux-v5.4/Documentation/vm/ |
| D | page_frags.rst | 34 only usable within the softirq context.
|
| /Linux-v5.4/Documentation/ |
| D | irqflags-tracing.txt | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v5.4/Documentation/trace/ |
| D | ftrace.rst | 820 # | / _---=> hardirq/softirq
873 # || / _---=> hardirq/softirq
931 hardirq/softirq:
934 - 'H' - hard irq occurred inside a softirq.
1329 # || / _---=> hardirq/softirq
1380 # || / _---=> hardirq/softirq
1457 # | / _---=> hardirq/softirq
1528 # || / _---=> hardirq/softirq
1566 # || / _---=> hardirq/softirq
1680 # || / _---=> hardirq/softirq
[all …]
|
| /Linux-v5.4/kernel/ |
| D | Makefile | 7 cpu.o exit.o softirq.o resource.o \
|
| /Linux-v5.4/Documentation/infiniband/ |
| D | core_locking.rst | 97 may be process context, softirq context, or interrupt context.
|
| /Linux-v5.4/Documentation/networking/ |
| D | netdevices.txt | 103 Context: softirq
|
| D | ppp_generic.txt | 218 from process context, not interrupt or softirq/BH context.
220 * The remaining generic layer functions may be called at softirq/BH
224 softirq/BH level but will not call it at interrupt level. Thus the
|
| /Linux-v5.4/Documentation/core-api/ |
| D | xarray.rst | 231 the array. It is safe to read the XArray from interrupt or softirq
235 context and then erase them in softirq context, you can do that this way::
254 /* foo_erase() is only called from softirq context */
263 If you are going to modify the XArray from interrupt or softirq context,
|
| /Linux-v5.4/Documentation/crypto/ |
| D | api-intro.txt | 84 methods may only be called from softirq and user contexts. For
|
