Home
last modified time | relevance | path

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

/Linux-v5.4/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
/Linux-v5.4/Documentation/virt/kvm/
Dppc-pv.txt26 hypercalls as described below.
28 KVM hypercalls
194 1) KVM hypercalls (ePAPR)
197 generic hypercalls are implemented here, like the ePAPR idle hcall. These are
200 2) PAPR hypercalls
202 PAPR hypercalls are needed to run server PowerPC PAPR guests (-M pseries in QEMU).
203 These are the same hypercalls that pHyp, the POWER hypervisor implements. Some of
207 3) OSI hypercalls
210 before KVM). This is supported to maintain compatibility. All these hypercalls get
Ds390-diag.txt4 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
5 native hypercalls and for selected hypercalls found on other s390
Dhypercalls.txt27 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
32 KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall
63 used to enumerate which hypercalls are available. On PPC, either device tree
Dapi.txt3306 This capability means the kernel is capable of handling hypercalls
3309 User space should expect that its handlers for these hypercalls
3318 The hypercalls mentioned above may or may not be processed successfully
4343 hypercalls and exit with this exit struct that contains all the guest gprs.
4363 The possible hypercalls are defined in the Power Architecture Platform
4533 This capability enables interception of OSI hypercalls that otherwise would
4534 be treated as normal system calls to be injected into the guest. OSI hypercalls
4548 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
4765 This capability controls whether individual sPAPR hypercalls (hcalls)
5288 hypercalls:
[all …]
/Linux-v5.4/arch/x86/include/asm/
DKbuild8 generated-y += xen-hypercalls.h
Dkvm_host.h982 u64 hypercalls; member
/Linux-v5.4/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.
/Linux-v5.4/Documentation/devicetree/bindings/arm/
Dxen.txt59 of UEFI runtime services implemented via hypercalls, see
/Linux-v5.4/Documentation/vm/
Dfrontswap.rst239 and use "batched" hypercalls.
/Linux-v5.4/Documentation/sparc/oradax/
Doracle-dax.rst265 can make hypercalls directly while the user code must use wrappers
/Linux-v5.4/arch/x86/kvm/
Dhyperv.c1548 ++vcpu->stat.hypercalls; in kvm_hv_hypercall_complete()
Dx86.c195 { "hypercalls", VCPU_STAT(hypercalls) },
7437 ++vcpu->stat.hypercalls; in kvm_emulate_hypercall()