| /Linux-v4.19/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-v4.19/fs/proc/ |
| D | stat.c | 85 u64 user, nice, system, idle, iowait, irq, softirq, steal; in show_stat() local
93 irq = softirq = steal = 0; in show_stat()
104 softirq += kcpustat_cpu(i).cpustat[CPUTIME_SOFTIRQ]; in show_stat()
126 seq_put_decimal_ull(p, " ", nsec_to_clock_t(softirq)); in show_stat()
140 softirq = kcpustat_cpu(i).cpustat[CPUTIME_SOFTIRQ]; in show_stat()
151 seq_put_decimal_ull(p, " ", nsec_to_clock_t(softirq)); in show_stat()
|
| /Linux-v4.19/arch/s390/kernel/ |
| D | vtime.c | 127 u64 timer, clock, user, guest, system, hardirq, softirq, steal; 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()
191 return virt_timer_forward(user + guest + system + hardirq + softirq); in do_account_vtime()
|
| /Linux-v4.19/Documentation/locking/ |
| D | lockdep-design.txt | 40 - softirq
68 A softirq-unsafe lock-class is automatically hardirq-unsafe as well. The
73 <softirq-safe> and <softirq-unsafe>
98 <softirq-safe> -> <softirq-unsafe>
102 thus could result in a lock inversion deadlock. Likewise, a softirq-safe
103 lock could be taken by an softirq context, interrupting a softirq-unsafe
116 - if a new softirq-safe lock is discovered, we check whether it took
117 any softirq-unsafe lock in the past.
122 - if a new softirq-unsafe lock is discovered, we check whether any
123 softirq-safe lock took it in the past.
[all …]
|
| /Linux-v4.19/Documentation/RCU/ |
| D | UP.txt | 14 Example 1: softirq Suicide
18 this same list in softirq context. Suppose that the process-context scan
19 is referencing element B when it is interrupted by softirq processing,
24 from softirq, the list scan would find itself referencing a newly freed
117 then, since RCU callbacks can be invoked from softirq context,
118 the callback might be called from a softirq that interrupted
|
| D | stallwarn.txt | 55 is running at a higher priority than the RCU softirq threads.
65 prevent RCU's kthreads and softirq handlers from running.
173 2-...: (3 GPs behind) idle=06c/0/0 softirq=1453/1455 fqs=0
174 16-...: (0 ticks this GP) idle=81c/0/0 softirq=764/764 fqs=0
199 The "softirq=" portion of the message tracks the number of RCU softirq
207 across repeated stall-warning messages, it is possible that RCU's softirq
210 kernels, if a high-priority process is starving RCU's softirq handler.
226 …0: (64628 ticks this GP) idle=dd5/3fffffffffffffff/0 softirq=82/543 last_accelerate: a345/d342 non…
|
| D | checklist.txt | 187 will be called from softirq context. In particular, it cannot
233 disabled, for example, in irq or softirq context. Commenting
351 with softirq disabled, e.g., via spin_lock_irqsave(),
354 the RCU softirq handler happens to run your RCU callback while
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/timers/ |
| D | highres.txt | 172 red-black tree to a separate double linked list and invokes the softirq
179 context to the softirq and to the task which is woken up by the expired
195 The softirq for running the hrtimer queues and executing the callbacks has been
196 separated from the tick bound timer softirq to allow accurate delivery of high
198 timers. The execution of this softirq can still be delayed by other softirqs,
|
| /Linux-v4.19/block/ |
| D | Makefile | 8 blk-exec.o blk-merge.o blk-softirq.o blk-timeout.o \
|
| /Linux-v4.19/Documentation/scheduler/ |
| D | sched-domains.txt | 29 through scheduler_tick(). It raises a softirq after the next regularly scheduled
32 in softirq context (SCHED_SOFTIRQ).
|
| /Linux-v4.19/Documentation/trace/ |
| D | ftrace.rst | 781 # | / _---=> hardirq/softirq
834 # || / _---=> hardirq/softirq
892 hardirq/softirq:
895 - 'H' - hard irq occurred inside a softirq.
1290 # || / _---=> hardirq/softirq
1341 # || / _---=> hardirq/softirq
1437 # || / _---=> hardirq/softirq
1475 # || / _---=> hardirq/softirq
1589 # || / _---=> hardirq/softirq
1642 # || / _---=> hardirq/softirq
[all …]
|
| /Linux-v4.19/Documentation/ |
| D | irqflags-tracing.txt | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v4.19/Documentation/vm/ |
| D | page_frags.rst | 34 only usable within the softirq context.
|
| /Linux-v4.19/Documentation/sysctl/ |
| D | net.txt | 108 of the driver for the per softirq cycle netdev_budget. This parameter influences
110 processing during RX softirq cycles. It is further meant for making current
119 Scales the maximum number of packets that can be processed during a TX softirq cycle.
121 net stack processing needs. Be careful to avoid making TX softirq processing a CPU hog.
|
| /Linux-v4.19/kernel/trace/ |
| D | trace_output.c | 453 int softirq; in trace_print_lat_fmt() local
458 softirq = entry->flags & TRACE_FLAG_SOFTIRQ; in trace_print_lat_fmt()
484 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
486 softirq ? 's' : in trace_print_lat_fmt()
|
| /Linux-v4.19/kernel/ |
| D | Makefile | 7 cpu.o exit.o softirq.o resource.o \
|
| /Linux-v4.19/Documentation/infiniband/ |
| D | core_locking.txt | 92 may be process context, softirq context, or interrupt context.
|
| /Linux-v4.19/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-v4.19/Documentation/core-api/ |
| D | local_ops.rst | 68 * This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
|
| /Linux-v4.19/Documentation/crypto/ |
| D | api-intro.txt | 84 methods may only be called from softirq and user contexts. For
|
