Home
last modified time | relevance | path

Searched refs:IPI (Results 1 – 25 of 45) sorted by relevance

12

/linux-6.15/Documentation/devicetree/bindings/mailbox/
H A Dxlnx,zynqmp-ipi-mailbox.yaml7 title: Xilinx IPI(Inter Processor Interrupt) mailbox controller
10 The Xilinx IPI(Inter Processor Interrupt) mailbox controller is to manage
11 messaging between two Xilinx Zynq UltraScale+ MPSoC IPI agents. Each IPI
15 | Xilinx ZynqMP IPI Controller |
27 Hardware | | IPI Agent | | IPI Buffers | |
32 | Xilinx IPI Agent Block |
107 It contains tx(0) or rx(1) channel IPI id number.
171 - description: Host IPI agent control register region
172 - description: Host IPI agent optional message buffers
233 /* buffered IPI */
[all …]
/linux-6.15/Documentation/translations/zh_CN/arch/loongarch/
H A Dirq-chip-model.rst26 在这种模型里面,IPI(Inter-Processor Interrupt)和CPU本地时钟中断直接发送到CPUINTC,
31 | IPI | --> | CPUINTC | <-- | Timer |
62 在这种模型里面,IPI(Inter-Processor Interrupt)和CPU本地时钟中断直接发送到CPUINTC,
67 | IPI | --> | CPUINTC | <-- | Timer |
93 在这种模型里面, IPI(Inter-Processor Interrupt) 和CPU本地时钟中断直接发送到CPUINTC,
98 | IPI |--> | CPUINTC(0-255vcpu)| <-- | Timer |
148 在这种模型里面,IPI(Inter-Processor Interrupt)和CPU本地时钟中断直接发送到CPUINTC,
154 | IPI | --> | CPUINTC | <-- | Timer |
/linux-6.15/Documentation/virt/kvm/
H A Dvcpu-requests.rst49 order to perform some KVM maintenance. To do so, an IPI is sent, forcing
55 1) Send an IPI. This forces a guest mode exit.
70 as well as to avoid sending unnecessary IPIs (see "IPI Reduction"), and
71 even to ensure IPI acknowledgements are waited upon (see "Waiting for
162 If, for example, the VCPU is sleeping, so no IPI is necessary, then
198 Reduction") must be certain when it's safe to not send the IPI. One
222 ...abort guest entry... ...send IPI...
233 IPI Reduction
249 KVM_REQUEST_WAIT flag changes the condition for sending an IPI from
256 As the determination of whether or not to send an IPI depends on the
[all …]
/linux-6.15/Documentation/translations/zh_TW/arch/loongarch/
H A Dirq-chip-model.rst26 在這種模型裏面,IPI(Inter-Processor Interrupt)和CPU本地時鐘中斷直接發送到CPUINTC,
31 | IPI | --> | CPUINTC | <-- | Timer |
62 在這種模型裏面,IPI(Inter-Processor Interrupt)和CPU本地時鐘中斷直接發送到CPUINTC,
67 | IPI | --> | CPUINTC | <-- | Timer |
/linux-6.15/Documentation/arch/loongarch/
H A Dirq-chip-model.rst22 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
28 | IPI | --> | CPUINTC | <-- | Timer |
59 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
65 | IPI | --> | CPUINTC | <-- | Timer |
91 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt
97 | IPI |--> | CPUINTC(0-255vcpu)| <-- | Timer |
155 In this model, IPI (Inter-Processor Interrupt) and CPU Local Timer interrupt go
161 | IPI | --> | CPUINTC | <-- | Timer |
/linux-6.15/Documentation/virt/kvm/loongarch/
H A Dhypercalls.rst88 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.
/linux-6.15/Documentation/translations/zh_CN/virt/
H A Dguest-halt-polling.rst25 IPI(以及处理IPI的相关成本)。
/linux-6.15/Documentation/features/sched/membarrier-sync-core/
H A Darch-support.txt11 # 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.
/linux-6.15/Documentation/devicetree/bindings/interrupt-controller/
H A Dthead,c900-aclint-sswi.yaml14 supervisor-level IPI functionality for a set of HARTs on a THEAD
15 platform. It provides a register to set an IPI (SETSSIP) for each
H A Dapple,aic.yaml37 a "local" fast IPI register as opposed to using the "global" fast IPI
/linux-6.15/Documentation/admin-guide/hw-vuln/
H A Dcore-scheduling.rst112 Once a task has been selected for all the siblings in the core, an IPI is sent to
113 siblings for whom a new task was selected. Siblings on receiving the IPI will
130 When the highest priority task is selected to run, a reschedule-IPI is sent to
142 (victim) to enter idle mode. This is because the sending of the IPI would bring
145 which may not be worth protecting. It is also possible that the IPI is received
171 IPI processing delays
173 Core scheduling selects only trusted tasks to run together. IPI is used to notify
175 receiving of the IPI on some arch (on x86, this has not been observed). This may
177 IPI. Even though cache is flushed on entry to user mode, victim tasks on siblings
/linux-6.15/Documentation/virt/kvm/devices/
H A Dxics.rst50 * Pending IPI (inter-processor interrupt) priority, 8 bits
51 Zero is the highest priority, 255 means no IPI is pending.
54 Zero means no interrupt pending, 2 means an IPI is pending
/linux-6.15/Documentation/devicetree/bindings/powerpc/fsl/
H A Dmpic.txt71 non-IPI interrupts to a single CPU at a time (EG: Freescale MPIC).
127 2 = MPIC inter-processor interrupt (IPI)
130 the MPIC IPI number. The type-specific
193 * MPIC IPI interrupts. Note the interrupt
/linux-6.15/Documentation/virt/
H A Dguest-halt-polling.rst12 a remote vCPU to avoid sending an IPI (and the associated
13 cost of handling the IPI) when performing a wakeup.
/linux-6.15/Documentation/translations/zh_CN/core-api/
H A Dthis_cpu_ops.rst245 除非绝对必要,否则强烈建议不要对每CPU数据结构进行远程写访问。请考虑使用IPI来唤醒
281 要进行代价高昂的同步。在这种情况下,通常建议使用IPI,而不是远程写入另一个处理器的
H A Dlocal_ops.rst147 /* IPI called on each CPU. */
/linux-6.15/arch/sh/kernel/cpu/sh4a/
H A Dsetup-sh7770.c339 HAC, IPI, SPDIF, HUDI, I2C, enumerator
365 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 } },
/linux-6.15/Documentation/RCU/Design/Expedited-Grace-Periods/
H A DExpedited-Grace-Periods.rst27 each of which results in an IPI to the target CPU.
48 The dotted arrows denote indirect action, for example, an IPI
55 ``smp_call_function_single()`` to send the CPU an IPI, which
96 | IPI the CPU to safely interact with the upcoming |
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 result
143 in splats, but failing to IPI online CPUs can result in too-short grace
231 For RCU-sched, there is an additional check: If the IPI has interrupted
245 bitmask of CPUs that must be IPIed, just before sending each IPI, and
246 (either explicitly or implicitly) within the IPI handler.
[all …]
/linux-6.15/kernel/irq/
H A DKconfig79 # Generic IRQ IPI support
85 # Generic IRQ IPI Mux support
/linux-6.15/drivers/mailbox/
H A DKconfig279 tristate "Xilinx ZynqMP IPI Mailbox"
282 Say yes here to add support for Xilinx IPI mailbox driver.
284 between processors with Xilinx ZynqMP IPI. It will place the
285 message to the IPI buffer and will access the IPI control
/linux-6.15/Documentation/virt/kvm/x86/
H A Dhypercalls.rst166 :Purpose: Hypercall used to yield if the IPI target vCPU is preempted
170 :Usage example: When sending a call-function IPI-many to vCPUs, yield if
171 any of the IPI target vCPUs was preempted.
/linux-6.15/arch/arc/kernel/
H A Dentry-arcv2.S51 VECTOR handle_interrupt ; (19) Inter core Interrupt (IPI)
53 VECTOR handle_interrupt ; (21) Software Triggered Intr (Self IPI)
/linux-6.15/Documentation/devicetree/bindings/power/reset/
H A Dxlnx,zynqmp-power.yaml68 // Example with IPI mailbox method:
/linux-6.15/drivers/rpmsg/
H A DKconfig41 This use IPI and IPC to communicate with remote processors.
/linux-6.15/lib/
H A DKconfig.kfence70 enabling and disabling static keys invoke IPI broadcasts, the latency

12