| /linux-3.4.99/include/trace/events/ |
| D | irq.h | 87 DECLARE_EVENT_CLASS(softirq,
112 DEFINE_EVENT(softirq, softirq_entry,
126 DEFINE_EVENT(softirq, softirq_exit,
140 DEFINE_EVENT(softirq, softirq_raise,
|
| /linux-3.4.99/kernel/ |
| D | softirq.c | 597 static void __local_trigger(struct call_single_data *cp, int softirq) in __local_trigger() argument
599 struct list_head *head = &__get_cpu_var(softirq_work_list[softirq]); in __local_trigger()
605 raise_softirq_irqoff(softirq); in __local_trigger()
613 int softirq; in remote_softirq_receive() local
615 softirq = cp->priv; in remote_softirq_receive()
618 __local_trigger(cp, softirq); in remote_softirq_receive()
622 static int __try_remote_softirq(struct call_single_data *cp, int cpu, int softirq) in __try_remote_softirq() argument
628 cp->priv = softirq; in __try_remote_softirq()
636 static int __try_remote_softirq(struct call_single_data *cp, int cpu, int softirq) in __try_remote_softirq() argument
654 void __send_remote_softirq(struct call_single_data *cp, int cpu, int this_cpu, int softirq) in __send_remote_softirq() argument
[all …]
|
| D | Makefile | 6 cpu.o exit.o itimer.o time.o softirq.o resource.o \
|
| /linux-3.4.99/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-3.4.99/Documentation/ |
| 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 …]
|
| D | irqflags-tracing.txt | 5 the "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| D | local_ops.txt | 52 - This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
|
| /linux-3.4.99/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 | checklist.txt | 167 written to be called from softirq context. In particular,
214 disabled, for example, in irq or softirq context. Commenting
313 with softirq disabled, e.g., via spin_lock_irqsave(),
316 the RCU softirq handler happens to run your RCU callback while
|
| D | stallwarn.txt | 168 is running at a higher priority than the RCU softirq threads.
|
| /linux-3.4.99/block/ |
| D | Makefile | 7 blk-exec.o blk-merge.o blk-softirq.o blk-timeout.o \
|
| /linux-3.4.99/include/linux/ |
| D | interrupt.h | 481 extern void send_remote_softirq(struct call_single_data *cp, int cpu, int softirq);
487 int this_cpu, int softirq);
|
| /linux-3.4.99/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-3.4.99/Documentation/trace/ |
| D | ftrace.txt | 300 # || / _---=> hardirq/softirq
345 hardirq/softirq:
346 'H' - hard irq occurred inside a softirq.
531 # || / _---=> hardirq/softirq
566 # || / _---=> hardirq/softirq
639 # || / _---=> hardirq/softirq
652 a softirq. (notice the 's'). But we also see that interrupts
671 # || / _---=> hardirq/softirq
724 thread's stack and we switched to the softirq stack (4K stacks
787 # || / _---=> hardirq/softirq
[all …]
|
| /linux-3.4.99/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-3.4.99/kernel/trace/ |
| D | trace_output.c | 569 int softirq; local
573 softirq = entry->flags & TRACE_FLAG_SOFTIRQ;
582 (hardirq && softirq) ? 'H' :
584 softirq ? 's' :
|
| /linux-3.4.99/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-3.4.99/Documentation/infiniband/ |
| D | core_locking.txt | 94 may be process context, softirq context, or interrupt context.
|
| /linux-3.4.99/Documentation/x86/x86_64/ |
| D | kernel-stacks | 25 The interrupt stack is also used when processing a softirq.
|
| /linux-3.4.99/tools/perf/util/ |
| D | trace-event-parse.c | 2632 int softirq; in print_lat_fmt() local
2639 softirq = lat_flags & TRACE_FLAG_SOFTIRQ; in print_lat_fmt()
2647 (hardirq && softirq) ? 'H' : in print_lat_fmt()
2648 hardirq ? 'h' : softirq ? 's' : '.'); in print_lat_fmt()
|
| /linux-3.4.99/Documentation/connector/ |
| D | connector.txt | 77 softirq context, but may silently fail under strong memory pressure.
|
| /linux-3.4.99/Documentation/crypto/ |
| D | api-intro.txt | 82 methods may only be called from softirq and user contexts. For
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | proc.txt | 493 softirqs softirq usage
867 Provides counts of softirq handlers serviced since boot time, for each cpu.
1168 softirq 183433 0 21755 12 39 1137 231 21459 2263
1181 - softirq: servicing softirqs
1206 The "softirq" line gives counts of softirqs serviced since boot time, for each
1209 softirq.
|
| /linux-3.4.99/arch/powerpc/platforms/ |
| D | Kconfig.cputype | 323 between system, softirq and hardirq state, so there is a
|