Home
last modified time | relevance | path

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

12

/linux-6.3-rc2/arch/x86/entry/syscalls/
A DMakefile60 $(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-6.3-rc2/Documentation/virt/kvm/
A 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
A Dapi.rst966 the contents of the hypercall page automatically; hypercalls will be
2651 (See Documentation/virt/kvm/arm/hypercalls.rst for more details.)
6741 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
7919 hypercalls:
7944 hypercalls:
7960 thinks it's running on Hyper-V and only use Hyper-V hypercalls.
8195 and also enable interception of guest hypercalls with KVM_EXIT_XEN.
8238 This capability means the kernel is capable of handling hypercalls
8241 User space should expect that its handlers for these hypercalls
8285 with KVM_EXIT_HYPERCALL exit reason to process some hypercalls.
[all …]
/linux-6.3-rc2/Documentation/virt/kvm/arm/
A Dindex.rst11 hypercalls
A Dpvtime.rst15 Two new SMCCC compatible hypercalls are defined:
/linux-6.3-rc2/Documentation/virt/kvm/x86/
A Dindex.rst13 hypercalls
A 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
/linux-6.3-rc2/Documentation/virt/kvm/s390/
A 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
/linux-6.3-rc2/arch/x86/include/asm/
A DKbuild9 generated-y += xen-hypercalls.h
/linux-6.3-rc2/Documentation/translations/zh_CN/virt/acrn/
A Dintroduction.rst48 与ACRN超级管理器的hypercalls进行交互来实现管理服务。HSM向用户空间输出一个char设备接口
A Dio-request.rst99 f. HSM将I/O请求状态更新为COMPLETE,并通过hypercalls通知超级管理器完成。
/linux-6.3-rc2/drivers/virt/acrn/
A DKconfig9 the ACRN Hypervisor through hypercalls. HSM will only run in
/linux-6.3-rc2/Documentation/virt/hyperv/
A Doverview.rst28 * Explicit hypercalls: Linux makes an explicit function call to
32 Hyper-V. On x86/x64, hypercalls use a Hyper-V specific calling
33 sequence. On arm64, hypercalls use the ARM standard SMCCC calling
41 hypercalls.
51 general Hyper-V functionality and provides details on the hypercalls
/linux-6.3-rc2/arch/arm64/kvm/
A DMakefile13 kvm-y += arm.o mmu.o mmio.o psci.o hypercalls.o pvtime.o \
/linux-6.3-rc2/Documentation/virt/acrn/
A Dintroduction.rst39 interacting with the ACRN Hypervisor via hypercalls. HSM exports a char device
A Dio-request.rst97 of the completion via hypercalls.
/linux-6.3-rc2/Documentation/powerpc/
A 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.
A Dpapr_hcalls.rst24 issue hypercalls to the hypervisor whenever it needs to perform an action
/linux-6.3-rc2/Documentation/translations/zh_CN/mm/
A Dfrontswap.rst166 KVM的客户方实现可以进行客户内压缩,并使用 “batched” hypercalls
/linux-6.3-rc2/Documentation/devicetree/bindings/arm/
A Dxen.txt61 of UEFI runtime services implemented via hypercalls, see
/linux-6.3-rc2/arch/x86/kvm/
A DKconfig138 passing Xen hypercalls to userspace.
/linux-6.3-rc2/tools/testing/selftests/kvm/
A DMakefile141 TEST_GEN_PROGS_aarch64 += aarch64/hypercalls
/linux-6.3-rc2/arch/powerpc/kvm/
A DKconfig142 hypercalls and page faults. The total, minimum and maximum
/linux-6.3-rc2/drivers/xen/
A DKconfig267 perform Xen hypercalls. This driver is normally required for systems
/linux-6.3-rc2/Documentation/mm/
A Dfrontswap.rst223 and use "batched" hypercalls.

Completed in 27 milliseconds

12