Searched refs:hypercalls (Results 1 – 17 of 17) sorted by relevance
| /Linux-v5.10/arch/x86/entry/syscalls/ |
| D | Makefile | 54 $(out)/xen-hypercalls.h: $(srctree)/scripts/xen-hypercalls.sh
55 $(call if_changed,hypercalls)
57 $(out)/xen-hypercalls.h: $(srctree)/include/xen/interface/xen*.h
63 syshdr-$(CONFIG_XEN) += xen-hypercalls.h
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| 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
|
| D | s390-diag.rst | 7 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
8 native hypercalls and for selected hypercalls found on other s390
|
| D | index.rst | 14 hypercalls
|
| D | hypercalls.rst | 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
71 used to enumerate which hypercalls are available. On PPC, either
|
| D | api.rst | 3667 This capability means the kernel is capable of handling hypercalls
3670 User space should expect that its handlers for these hypercalls
3679 The hypercalls mentioned above may or may not be processed successfully
5070 hypercalls and exit with this exit struct that contains all the guest gprs.
5092 The possible hypercalls are defined in the Power Architecture Platform
5377 This capability enables interception of OSI hypercalls that otherwise would
5378 be treated as normal system calls to be injected into the guest. OSI hypercalls
5393 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
5632 This capability controls whether individual sPAPR hypercalls (hcalls)
6264 hypercalls:
[all …]
|
| /Linux-v5.10/arch/x86/include/asm/ |
| D | Kbuild | 8 generated-y += xen-hypercalls.h
|
| D | kvm_host.h | 1054 u64 hypercalls; member
|
| /Linux-v5.10/arch/arm64/kvm/ |
| D | Makefile | 15 arm.o mmu.o mmio.o psci.o perf.o hypercalls.o pvtime.o \
|
| /Linux-v5.10/Documentation/powerpc/ |
| 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
251 The full specification for all hypercalls/ultracalls will eventually
856 This document describes the Hypervisor calls (hypercalls) that are
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
871 The full specification for all hypercalls/ultracalls will eventually
878 Following are the set of hypercalls needed to support Ultravisor.
|
| D | papr_hcalls.rst | 24 issue hypercalls to the hypervisor whenever it needs to perform an action
|
| /Linux-v5.10/Documentation/devicetree/bindings/arm/ |
| D | xen.txt | 59 of UEFI runtime services implemented via hypercalls, see
|
| /Linux-v5.10/Documentation/virt/kvm/arm/ |
| D | pvtime.rst | 15 Two new SMCCC compatible hypercalls are defined:
|
| /Linux-v5.10/Documentation/vm/ |
| D | frontswap.rst | 239 and use "batched" hypercalls.
|
| /Linux-v5.10/Documentation/sparc/oradax/ |
| D | oracle-dax.rst | 265 can make hypercalls directly while the user code must use wrappers
|
| /Linux-v5.10/arch/x86/kvm/ |
| D | hyperv.c | 1690 ++vcpu->stat.hypercalls; in kvm_hv_hypercall_complete()
|
| D | x86.c | 220 VCPU_STAT("hypercalls", hypercalls),
8134 ++vcpu->stat.hypercalls; in kvm_emulate_hypercall()
|
