Searched full:ipis (Results 1 – 19 of 19) sorted by relevance
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | apple,aic.yaml | 24 - 2 per-CPU IPIs (meant as "self" and "other", but they are interchangeable
34 IPIs may be performed via MMIO registers on all variants of AIC. Starting
35 from A11, system registers may also be used for "fast" IPIs. Starting from
36 M1, even faster IPIs within the same cluster may be achieved by writing to
|
| D | mti,gic.yaml | 16 interrupts which can be used as IPIs. The GIC also includes a free-running
55 Specifies the range of GIC interrupts that are reserved for IPIs.
|
| D | brcm,bcm2836-l1-intc.yaml | 15 events, and SMP IPIs. One of the CPUs may receive interrupts for the
|
| D | riscv,cpu-intc.yaml | 18 external interrupts. Software interrupts are used to send IPIs between
|
| D | apple,aic2.yaml | 29 FIQ-based Fast IPIs.
|
| /Documentation/virt/kvm/x86/ |
| D | hypercalls.rst | 145 :Purpose: Send IPIs to multiple vCPUs.
152 The hypercall lets a guest send multicast IPIs, with at most 128
159 Returns the number of CPUs to which the IPIs were delivered successfully.
|
| D | cpuid.rst | 79 send IPIs
|
| D | timekeeping.rst | 275 CPU, used for IPIs and local timer interrupts.
|
| /Documentation/virt/kvm/loongarch/ |
| D | hypercalls.rst | 74 :Purpose: Send IPIs to multiple vCPUs.
81 The hypercall lets a guest send multiple IPIs (Inter-Process Interrupts) with
|
| /Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 70 as well as to avoid sending unnecessary IPIs (see "IPI Reduction"), and
161 proceeding. This flag only applies to VCPUs that would receive IPIs.
195 IPIs will only trigger guest mode exits for VCPU threads that are in guest
244 Some requests, those with the KVM_REQUEST_WAIT flag set, require IPIs to
|
| /Documentation/power/ |
| D | suspend-and-interrupts.rst | 41 but also to IPIs and to some other special-purpose interrupts.
|
| /Documentation/arch/x86/ |
| D | microcode.rst | 138 While this took care of device or external interrupts, IPIs including
|
| /Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 88 | IPIs. |
102 | these IPIs is to build your kernel with ``CONFIG_NO_HZ_FULL=y``. RCU |
506 operations. The dyntick-idle counters are used to avoid sending IPIs to
|
| /Documentation/core-api/ |
| D | this_cpu_ops.rst | 330 may be necessary. IPIs are generally recommended in such scenarios instead
|
| /Documentation/networking/ |
| D | scaling.rst | 180 introduce inter-processor interrupts (IPIs))
202 the end of the bottom half routine, IPIs are sent to any CPUs for which
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 158 1. Avoid sending scheduler IPIs to the CPU to be de-jittered,
|
| D | kernel-parameters.txt | 4077 nonmi_ipi [X86] Disable using NMI IPIs during panic/reboot to
5176 enlist help from cond_resched() and sched IPIs to
5688 avoid sending IPIs, starting with the beginning
|
| /Documentation/RCU/ |
| D | checklist.rst | 442 never sends IPIs to other CPUs, so it is easier on
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 2126 | | IPIs. | | |
2643 workloads that don't want their ``nohz_full`` CPUs receiving IPIs and
2660 Tasks Trace RCU that uses scheduler locking and IPIs to synchronize with
2661 readers. Real-time systems that cannot tolerate IPIs may build their
2662 kernels with ``CONFIG_TASKS_TRACE_RCU_READ_MB=y``, which avoids the IPIs at
|