Home
last modified time | relevance | path

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

/Linux-v5.15/arch/x86/entry/syscalls/
DMakefile61 $(out)/xen-hypercalls.h: $(srctree)/scripts/xen-hypercalls.sh FORCE
62 $(call if_changed,hypercalls)
64 $(out)/xen-hypercalls.h: $(srctree)/include/xen/interface/xen*.h
71 syshdr-$(CONFIG_XEN) += xen-hypercalls.h
/Linux-v5.15/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.rst974 automatically; hypercalls will be intercepted and passed to userspace
5587 hypercalls and exit with this exit struct that contains all the guest gprs.
5609 The possible hypercalls are defined in the Power Architecture Platform
5922 This capability enables interception of OSI hypercalls that otherwise would
5923 be treated as normal system calls to be injected into the guest. OSI hypercalls
5938 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
6177 This capability controls whether individual sPAPR hypercalls (hcalls)
6956 hypercalls:
6981 hypercalls:
6991 hypercalls are handled by Level 0 hypervisor (Hyper-V) bypassing KVM.
[all …]
/Linux-v5.15/arch/x86/include/asm/
DKbuild9 generated-y += xen-hypercalls.h
Dkvm_host.h1265 u64 hypercalls; member
/Linux-v5.15/Documentation/translations/zh_CN/virt/acrn/
Dintroduction.rst48 与ACRN超级管理器的hypercalls进行交互来实现管理服务。HSM向用户空间输出一个char设备接口
Dio-request.rst99 f. HSM将I/O请求状态更新为COMPLETE,并通过hypercalls通知超级管理器完成。
/Linux-v5.15/drivers/virt/acrn/
DKconfig9 the ACRN Hypervisor through hypercalls. HSM will only run in
/Linux-v5.15/arch/arm64/kvm/
DMakefile15 arm.o mmu.o mmio.o psci.o perf.o hypercalls.o pvtime.o \
/Linux-v5.15/Documentation/virt/acrn/
Dintroduction.rst39 interacting with the ACRN Hypervisor via hypercalls. HSM exports a char device
Dio-request.rst97 of the completion via hypercalls.
/Linux-v5.15/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
/Linux-v5.15/Documentation/devicetree/bindings/arm/
Dxen.txt59 of UEFI runtime services implemented via hypercalls, see
/Linux-v5.15/Documentation/virt/kvm/arm/
Dpvtime.rst15 Two new SMCCC compatible hypercalls are defined:
/Linux-v5.15/arch/x86/kvm/
DKconfig121 passing Xen hypercalls to userspace.
Dhyperv.c2038 ++vcpu->stat.hypercalls; in kvm_hv_hypercall_complete()
Dx86.c273 STATS_DESC_COUNTER(VCPU, hypercalls),
8666 ++vcpu->stat.hypercalls; in complete_hypercall_exit()
8766 ++vcpu->stat.hypercalls; in kvm_emulate_hypercall()
/Linux-v5.15/Documentation/vm/
Dfrontswap.rst239 and use "batched" hypercalls.
/Linux-v5.15/Documentation/sparc/oradax/
Doracle-dax.rst265 can make hypercalls directly while the user code must use wrappers