Searched refs:IPI (Results 1 – 25 of 29) sorted by relevance
12
49 order to perform some KVM maintenance. To do so, an IPI is sent, forcing55 1) Send an IPI. This forces a guest mode exit.70 as well as to avoid sending unnecessary IPIs (see "IPI Reduction"), and71 even to ensure IPI acknowledgements are waited upon (see "Waiting for160 then the caller will wait for each VCPU to acknowledge its IPI before162 If, for example, the VCPU is sleeping, so no IPI is necessary, then192 kick will send an IPI to force an exit from guest mode when necessary.197 enter guest mode. This means that an optimized implementation (see "IPI198 Reduction") must be certain when it's safe to not send the IPI. One208 !kvm_request_pending() on its last check and then not receiving an IPI for[all …]
26 在這種模型裏面，IPI（Inter-Processor Interrupt）和CPU本地時鐘中斷直接發送到CPUINTC，31 | IPI | --> | CPUINTC | <-- | Timer |62 在這種模型裏面，IPI（Inter-Processor Interrupt）和CPU本地時鐘中斷直接發送到CPUINTC，67 | IPI | --> | CPUINTC | <-- | Timer |
88 PV IPI on LoongArch includes both PV IPI multicast sending and PV IPI receiving,89 and SWI is used for PV IPI inject since there is no VM-exits accessing SWI registers.
25 IPI（以及处理IPI的相关成本）。
11 # when returning from IPI handler, and when returning to user-space.31 # x86-32 uses IRET as return from interrupt, which takes care of the IPI.35 # x86-64 uses IRET as return from interrupt, which takes care of the IPI.
112 Once a task has been selected for all the siblings in the core, an IPI is sent to113 siblings for whom a new task was selected. Siblings on receiving the IPI will130 When the highest priority task is selected to run, a reschedule-IPI is sent to142 (victim) to enter idle mode. This is because the sending of the IPI would bring145 which may not be worth protecting. It is also possible that the IPI is received171 IPI processing delays173 Core scheduling selects only trusted tasks to run together. IPI is used to notify175 receiving of the IPI on some arch (on x86, this has not been observed). This may177 IPI. Even though cache is flushed on entry to user mode, victim tasks on siblings
50 * Pending IPI (inter-processor interrupt) priority, 8 bits51 Zero is the highest priority, 255 means no IPI is pending.54 Zero means no interrupt pending, 2 means an IPI is pending
61 interrupt of the device being passed-through or the initial IPI ESB
12 a remote vCPU to avoid sending an IPI (and the associated13 cost of handling the IPI) when performing a wakeup.
245 除非绝对必要，否则强烈建议不要对每CPU数据结构进行远程写访问。请考虑使用IPI来唤醒281 要进行代价高昂的同步。在这种情况下，通常建议使用IPI，而不是远程写入另一个处理器的
147 /* IPI called on each CPU. */
27 each of which results in an IPI to the target CPU.48 The dotted arrows denote indirect action, for example, an IPI55 ``smp_call_function_single()`` to send the CPU an IPI, which96 | IPI the CPU to safely interact with the upcoming |105 | IPI the CPU. |128 that the CPU went idle while the IPI was in flight. If the CPU is idle,142 grace periods. In addition, attempting to IPI offline CPUs will result143 in splats, but failing to IPI online CPUs can result in too-short grace231 For RCU-sched, there is an additional check: If the IPI has interrupted235 For RCU-preempt, there is no specific check for idle in the IPI handler[all …]
339 HAC, IPI, SPDIF, HUDI, I2C, enumerator365 INTC_VECT(HAC, 0x580), INTC_VECT(IPI, 0x5c0),425 DMAC, I2C, HUDI, SPDIF, IPI, HAC, TMU, GPIO } },430 { 0xffe00004, 0, 32, 8, /* INT2PRI1 */ { IPI, SPDIF, HUDI, I2C } },
75 # Generic IRQ IPI support81 # Generic IRQ IPI Mux support
166 :Purpose: Hypercall used to yield if the IPI target vCPU is preempted170 :Usage example: When sending a call-function IPI-many to vCPUs, yield if171 any of the IPI target vCPUs was preempted.
51 VECTOR handle_interrupt ; (19) Inter core Interrupt (IPI)53 VECTOR handle_interrupt ; (21) Software Triggered Intr (Self IPI)
41 This use IPI and IPC to communicate with remote processors.
70 enabling and disabling static keys invoke IPI broadcasts, the latency
1716 to the smp_call_function*() IPI wrappers. These debug prints1717 include the IPI handler function currently executing (if any)
57 1 Soft-irq. Uses IPI to complete IOs across CPU nodes. Simulates the overhead
153 /* IPI called on each CPU. */
160 global clock event devices. The support of such hardware would involve IPI
222 IPI-sensitive real-time workloads can use the rcupdate.rcu_normal
1170 to each of the threads, where the IPI handler will also write
916 0x8000001c, 0, ecx, 29, lwp_ip_filtering , IP filtering (IPI, IPF, BaseIP, and LimitIP @ LWPCP) supported