Lines Matching +full:ipi +full:- +full:id

1 .. SPDX-License-Identifier: GPL-2.0
8  KVM Hypercalls have a three-byte sequence of either the vmcall or the vmmcall
18   R2-R7 are used for parameters 1-6. In addition, R1 is used for hypercall
25   refer to Documentation/virt/kvm/s390/s390-diag.rst.
28   It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.
31   KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
33   For more information refer to Documentation/virt/kvm/ppc-pv.rst
37   number in $2 (v0). Up to four arguments may be placed in $4-$7 (a0-a3) and
50 ------------------------
58 ----------------
66 ------------------
77 ----------------------------
87 ------------------
95   execute HLT instruction once it has busy-waited for more than a threshold
96   time-interval. Execution of HLT instruction would cause the hypervisor to put
99   specifying APIC ID (a1) of the vcpu to be woken up. An additional argument (a0)
104 -----------------------
141 ------------------
147 - a0: lower part of the bitmap of destination APIC IDs
148 - a1: higher part of the bitmap of destination APIC IDs
149 - a2: the lowest APIC ID in bitmap
150 - a3: APIC ICR
153 128 destinations per hypercall in 64-bit mode and 64 vCPUs per
154 hypercall in 32-bit mode.  The destinations are represented by a
156 a0 corresponds to the APIC ID in the third argument (a2), bit 1
157 corresponds to the APIC ID a2+1, and so on.
162 ---------------------
166 :Purpose: Hypercall used to yield if the IPI target vCPU is preempted
168 a0: destination APIC ID
170 :Usage example: When sending a call-function IPI-many to vCPUs, yield if
171 	        any of the IPI target vCPUs was preempted.
174 -------------------------
184         * bits  3:0 - preferred page size encoding 0 = 4kb, 1 = 2mb, 2 = 1gb, etc...
185         * bit     4 - plaintext = 0, encrypted = 1
186         * bits 63:5 - reserved (must be zero)