Home
last modified time | relevance | path

Searched refs:hypercalls (Results 1 – 18 of 18) sorted by relevance

/kernel/linux/linux-5.10/arch/x86/entry/syscalls/
DMakefile54 $(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
/kernel/linux/linux-5.10/Documentation/virt/kvm/
Dppc-pv.rst29 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
Ds390-diag.rst7 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
8 native hypercalls and for selected hypercalls found on other s390
Dindex.rst14 hypercalls
Dhypercalls.rst31 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
Dapi.rst3673 This capability means the kernel is capable of handling hypercalls
3676 User space should expect that its handlers for these hypercalls
3685 The hypercalls mentioned above may or may not be processed successfully
5078 hypercalls and exit with this exit struct that contains all the guest gprs.
5100 The possible hypercalls are defined in the Power Architecture Platform
5385 This capability enables interception of OSI hypercalls that otherwise would
5386 be treated as normal system calls to be injected into the guest. OSI hypercalls
5401 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
5640 This capability controls whether individual sPAPR hypercalls (hcalls)
6272 hypercalls:
[all …]
/kernel/linux/linux-5.10/arch/x86/include/asm/
DKbuild8 generated-y += xen-hypercalls.h
Dkvm_host.h1059 u64 hypercalls; member
/kernel/linux/linux-5.10/arch/arm64/kvm/
DMakefile15 arm.o mmu.o mmio.o psci.o perf.o hypercalls.o pvtime.o \
/kernel/linux/linux-5.10/Documentation/powerpc/
Dultravisor.rst42 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.
Dpapr_hcalls.rst24 issue hypercalls to the hypervisor whenever it needs to perform an action
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Dxen.txt59 of UEFI runtime services implemented via hypercalls, see
/kernel/linux/linux-5.10/Documentation/virt/kvm/arm/
Dpvtime.rst15 Two new SMCCC compatible hypercalls are defined:
/kernel/linux/linux-5.10/Documentation/vm/
Dfrontswap.rst239 and use "batched" hypercalls.
/kernel/linux/linux-5.10/Documentation/sparc/oradax/
Doracle-dax.rst265 can make hypercalls directly while the user code must use wrappers
/kernel/linux/linux-5.10/arch/x86/kvm/
Dhyperv.c1699 ++vcpu->stat.hypercalls; in kvm_hv_hypercall_complete()
Dx86.c221 VCPU_STAT("hypercalls", hypercalls),
8380 ++vcpu->stat.hypercalls; in kvm_emulate_hypercall()
/kernel/linux/patches/linux-5.10/imx8mm_patch/patches/
D0001_linux_arch.patch15491 diff --git a/arch/arm64/kvm/hypercalls.c b/arch/arm64/kvm/hypercalls.c
15493 --- a/arch/arm64/kvm/hypercalls.c
15494 +++ b/arch/arm64/kvm/hypercalls.c