| /linux-4.4.14/include/trace/events/ |
| D | irq.h | 102 DECLARE_EVENT_CLASS(softirq,
127 DEFINE_EVENT(softirq, softirq_entry,
141 DEFINE_EVENT(softirq, softirq_exit,
155 DEFINE_EVENT(softirq, softirq_raise,
|
| /linux-4.4.14/fs/proc/ |
| D | stat.c | 84 u64 user, nice, system, idle, iowait, irq, softirq, steal; in show_stat() local
92 irq = softirq = steal = 0; in show_stat()
104 softirq += kcpustat_cpu(i).cpustat[CPUTIME_SOFTIRQ]; in show_stat()
127 seq_put_decimal_ull(p, ' ', cputime64_to_clock_t(softirq)); in show_stat()
141 softirq = kcpustat_cpu(i).cpustat[CPUTIME_SOFTIRQ]; in show_stat()
152 seq_put_decimal_ull(p, ' ', cputime64_to_clock_t(softirq)); in show_stat()
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | tracepoint.xml.db | 3 API-trace-softirq-entry
4 API-trace-softirq-exit
5 API-trace-softirq-raise
|
| /linux-4.4.14/Documentation/locking/ |
| D | lockdep-design.txt | 39 - 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-4.4.14/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 | 101 0: (63959 ticks this GP) idle=241/3fffffffffffffff/0 softirq=82/543
107 …0: (64628 ticks this GP) idle=dd5/3fffffffffffffff/0 softirq=82/543 last_accelerate: a345/d342 non…
124 The "softirq=" portion of the message tracks the number of RCU softirq
132 across repeated stall-warning messages, it is possible that RCU's softirq
135 kernels, if a high-priority process is starving RCU's softirq handler.
230 is running at a higher priority than the RCU softirq threads.
|
| D | checklist.txt | 171 must be written to be called from softirq context. In particular,
219 disabled, for example, in irq or softirq context. Commenting
337 with softirq disabled, e.g., via spin_lock_irqsave(),
340 the RCU softirq handler happens to run your RCU callback while
|
| D | whatisRCU.txt | 457 This invocation might happen from either softirq or process context,
911 of softirq monopolization of one or more of the CPUs? For
|
| /linux-4.4.14/block/ |
| D | Makefile | 7 blk-exec.o blk-merge.o blk-softirq.o blk-timeout.o \
|
| /linux-4.4.14/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-4.4.14/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-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 569 # | / _---=> hardirq/softirq
622 # || / _---=> hardirq/softirq
680 hardirq/softirq:
681 'H' - hard irq occurred inside a softirq.
953 # || / _---=> hardirq/softirq
1004 # || / _---=> hardirq/softirq
1099 # || / _---=> hardirq/softirq
1136 # || / _---=> hardirq/softirq
1249 # || / _---=> hardirq/softirq
1302 # || / _---=> hardirq/softirq
[all …]
|
| /linux-4.4.14/kernel/trace/ |
| D | trace_output.c | 391 int softirq; in trace_print_lat_fmt() local
394 softirq = entry->flags & TRACE_FLAG_SOFTIRQ; in trace_print_lat_fmt()
418 (hardirq && softirq) ? 'H' : in trace_print_lat_fmt()
420 softirq ? 's' : in trace_print_lat_fmt()
|
| /linux-4.4.14/Documentation/ |
| D | irqflags-tracing.txt | 5 the "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| D | local_ops.txt | 57 - This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
|
| D | kernel-per-CPU-kthreads.txt | 65 Purpose: Execute softirq handlers when threaded or when under heavy load.
66 To reduce its OS jitter, each softirq vector must be handled
|
| /linux-4.4.14/kernel/ |
| D | Makefile | 6 cpu.o exit.o softirq.o resource.o \
|
| /linux-4.4.14/Documentation/networking/ |
| D | netdevices.txt | 106 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-4.4.14/Documentation/infiniband/ |
| D | core_locking.txt | 94 may be process context, softirq context, or interrupt context.
|
| /linux-4.4.14/Documentation/crypto/ |
| D | api-intro.txt | 82 methods may only be called from softirq and user contexts. For
|
| /linux-4.4.14/Documentation/x86/ |
| D | kernel-stacks | 28 The interrupt stack is also used when processing a softirq.
|
| /linux-4.4.14/Documentation/connector/ |
| D | connector.txt | 79 softirq context, but may silently fail under strong memory pressure.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | proc.txt | 606 softirqs softirq usage
988 Provides counts of softirq handlers serviced since boot time, for each cpu.
1288 softirq 183433 0 21755 12 39 1137 231 21459 2263
1301 - softirq: servicing softirqs
1327 The "softirq" line gives counts of softirqs serviced since boot time, for each
1330 softirq.
|
| /linux-4.4.14/init/ |
| D | Kconfig | 359 between system, softirq and hardirq state, so there is a
388 transitions between softirq and hardirq state, so there can be a
728 from kthreads rather than from softirq context) to be specified
739 invoke their own RCU callbacks in softirq context.
752 All other CPUs will invoke their own RCU callbacks in softirq
|
| /linux-4.4.14/tools/lib/traceevent/ |
| D | event-parse.c | 5086 int softirq; in pevent_data_lat_fmt() local
5114 softirq = lat_flags & TRACE_FLAG_SOFTIRQ; in pevent_data_lat_fmt()
5122 (hardirq && softirq) ? 'H' : in pevent_data_lat_fmt()
5123 hardirq ? 'h' : softirq ? 's' : '.'); in pevent_data_lat_fmt()
|
| /linux-4.4.14/arch/ |
| D | Kconfig | 499 This spares a stack switch and improves cache usage on softirq
|