| /linux/arch/x86/entry/syscalls/ |
| H A D | Makefile | 24 quiet_cmd_hypercalls = HYPERCALLS $@
60 $(out)/xen-hypercalls.h: $(srctree)/scripts/xen-hypercalls.sh FORCE
61 $(call if_changed,hypercalls)
63 $(out)/xen-hypercalls.h: $(srctree)/include/xen/interface/xen*.h
70 syshdr-$(CONFIG_XEN) += xen-hypercalls.h
|
| /linux/Documentation/virt/kvm/ |
| H A D | ppc-pv.rst | 29 hypercalls as described below.
31 KVM hypercalls
204 1) KVM hypercalls (ePAPR)
207 generic hypercalls are implemented here, like the ePAPR idle hcall. These are
210 2) PAPR hypercalls
212 PAPR hypercalls are needed to run server PowerPC PAPR guests (-M pseries in QEMU).
213 These are the same hypercalls that pHyp, the POWER hypervisor, implements. Some of
217 3) OSI hypercalls
220 before KVM). This is supported to maintain compatibility. All these hypercalls get
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | hypercalls.rst | 8 KVM Hypercalls have a three-byte sequence of either the vmcall or the vmmcall
31 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
36 KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall
40 KVM Hypercalls Documentation
71 used to enumerate which hypercalls are available. On PPC, either
|
| H A D | index.rst | 13 hypercalls
|
| /linux/include/uapi/linux/ |
| H A D | kvm_para.h | 13 /* Return values for hypercalls */
35 * hypercalls use architecture specific
|
| /linux/Documentation/virt/kvm/loongarch/ |
| H A D | hypercalls.rst | 7 KVM hypercalls use the HVCL instruction with code 0x100 and the hypercall
28 capable KVM, you may now use hypercalls as described below.
63 KVM Hypercalls Documentation
|
| H A D | index.rst | 10 hypercalls.rst
|
| /linux/Documentation/arch/powerpc/ |
| H A D | ultravisor.rst | 42 leak. All hypercalls except H_RANDOM are reflected to the hypervisor.
117 * When a process is running in secure mode all hypercalls
172 For hypercalls, the Ultravisor inserts neutral state into all
191 * Hypercalls: special system calls used to request services from
251 The full specification for all hypercalls/ultracalls will eventually
856 This document describes the Hypervisor calls (hypercalls) that are
857 needed to support the Ultravisor. Hypercalls are services provided by
860 Register usage for these hypercalls is identical to that of the other
861 hypercalls defined in the Power Architecture Platform Reference (PAPR)
868 This document only covers hypercalls currently implemented/planned
[all …]
|
| /linux/arch/x86/include/asm/ |
| H A D | vmware.h | 12 * - Low bandwidth (LB) hypercalls (I/O port based, vmcall and vmmcall)
21 * - Low bandwidth TDX hypercalls (x86_64 only) are similar to LB
22 * hypercalls. They also have up to 6 input and 6 output on registers
27 * - High bandwidth (HB) hypercalls are I/O port based only. They have
|
| /linux/tools/testing/selftests/kvm/arm64/ |
| H A D | hypercalls.c | 3 /* hypercalls: Check the ARM64's psuedo-firmware bitmap register interface.
8 * hypercalls are properly masked or unmasked to the guest when disabled or
94 /* Feature support check against a different family of hypercalls */
|
| /linux/Documentation/virt/hyperv/ |
| H A D | coco.rst | 158 Hyper-V Hypercalls
160 When in fully-enlightened mode, hypercalls made by the Linux guest are routed
162 normal hypercalls trap to the paravisor first, which may in turn invoke the
164 hypercalls made by the Linux guest must always be routed directly to the
233 "use_calls" flag indicating to use hypercalls.
361 SIEFP, as well as hypercalls like HvPostMessage and HvSignalEvent). If the
|
| /linux/tools/testing/selftests/kvm/x86/ |
| H A D | hyperv_tlb_flush.c | 40 /* HvFlushVirtualAddressSpace, HvFlushVirtualAddressList hypercalls */
48 /* HvFlushVirtualAddressSpaceEx, HvFlushVirtualAddressListEx hypercalls */
199 /* "Slow" hypercalls */ in sender_guest_code()
355 /* "Fast" hypercalls */ in sender_guest_code()
619 * for 'workers' and issues TLB flush hypercalls. in main()
|
| H A D | hyperv_extended_hypercalls.c | 48 /* Verify if extended hypercalls are supported */ in main()
|
| /linux/drivers/virt/acrn/ |
| H A D | Kconfig | 9 the ACRN Hypervisor through hypercalls. HSM will only run in
|
| /linux/arch/x86/xen/ |
| H A D | trace.c | 8 #include <asm/xen-hypercalls.h>
|
| H A D | multicalls.c | 5 * Xen allows multiple hypercalls to be issued at once, using the
107 /* Number of parameters of hypercalls used via multicalls. */
|
| /linux/arch/arm64/include/asm/ |
| H A D | kvm_asm.h | 57 /* Hypercalls that are unavailable once pKVM has finalised. */
70 /* Hypercalls that are always available and common to [nh]VHE/pKVM. */
95 /* Hypercalls that are available only when pKVM has finalised. */
|
| /linux/arch/x86/boot/ |
| H A D | io.h | 24 * TDX guests override these to use hypercalls.
|
| /linux/arch/x86/boot/compressed/ |
| H A D | tdx.c | 73 /* Use hypercalls instead of I/O instructions */ in early_tdx_detect()
|
| /linux/arch/x86/coco/tdx/ |
| H A D | tdx-shared.c | 57 * process by cutting number of hypercalls (if successful). in tdx_accept_memory()
|
| /linux/tools/testing/selftests/kvm/include/x86/ |
| H A D | hyperv.h | 202 /* Hypercalls */
227 /* Extended hypercalls */
|
| /linux/Documentation/virt/acrn/ |
| H A D | introduction.rst | 39 interacting with the ACRN Hypervisor via hypercalls. HSM exports a char device
|
| /linux/arch/s390/include/asm/ |
| H A D | kvm_para.h | 10 * Hypercalls for KVM on s390. The calling convention is similar to the
|
| /linux/include/asm-generic/ |
| H A D | mshyperv.h | 128 * Rep hypercalls. Callers of this functions are supposed to ensure that
221 * in making hypercalls and such that talk about specific
|
| /linux/arch/arm/xen/ |
| H A D | hypercall.S | 37 * Xen hypercalls have 5 arguments at most, the fifth paramter is passed
|