Searched refs:hypercalls (Results 1 – 25 of 28) sorted by relevance
12
61 $(out)/xen-hypercalls.h: $(srctree)/scripts/xen-hypercalls.sh FORCE62 $(call if_changed,hypercalls)64 $(out)/xen-hypercalls.h: $(srctree)/include/xen/interface/xen*.h71 syshdr-$(CONFIG_XEN) += xen-hypercalls.h
29 hypercalls as described below.31 KVM hypercalls204 1) KVM hypercalls (ePAPR)207 generic hypercalls are implemented here, like the ePAPR idle hcall. These are210 2) PAPR hypercalls212 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 of217 3) OSI hypercalls220 before KVM). This is supported to maintain compatibility. All these hypercalls get
7 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for8 native hypercalls and for selected hypercalls found on other s390
14 hypercalls
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 hypercall71 used to enumerate which hypercalls are available. On PPC, either
991 automatically; hypercalls will be intercepted and passed to userspace6143 This capability enables interception of PAPR hypercalls. PAPR hypercalls are6382 This capability controls whether individual sPAPR hypercalls (hcalls)7175 hypercalls:7200 hypercalls:7216 thinks it's running on Hyper-V and only use Hyper-V hypercalls.7411 and also enable interception of guest hypercalls with KVM_EXIT_XEN.7430 This capability means the kernel is capable of handling hypercalls7433 User space should expect that its handlers for these hypercalls7477 with KVM_EXIT_HYPERCALL exit reason to process some hypercalls.[all …]
9 generated-y += xen-hypercalls.h
1272 u64 hypercalls; member
48 与ACRN超级管理器的hypercalls进行交互来实现管理服务。HSM向用户空间输出一个char设备接口
99 f. HSM将I/O请求状态更新为COMPLETE，并通过hypercalls通知超级管理器完成。
9 the ACRN Hypervisor through hypercalls. HSM will only run in
15 arm.o mmu.o mmio.o psci.o perf.o hypercalls.o pvtime.o \
14 hypercalls.o/
1 …hypercalls.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/aarch64/b…3 source_arch/arm64/kvm/hypercalls.o := arch/arm64/kvm/hypercalls.c5 deps_arch/arm64/kvm/hypercalls.o := \1280 arch/arm64/kvm/hypercalls.o: $(deps_arch/arm64/kvm/hypercalls.o)1282 $(deps_arch/arm64/kvm/hypercalls.o):
1 …/kvm/mmio.o arch/arm64/kvm/psci.o arch/arm64/kvm/perf.o arch/arm64/kvm/hypercalls.o arch/arm64/kvm…
42 leak. All hypercalls except H_RANDOM are reflected to the hypervisor.117 * When a process is running in secure mode all hypercalls172 For hypercalls, the Ultravisor inserts neutral state into all251 The full specification for all hypercalls/ultracalls will eventually856 This document describes the Hypervisor calls (hypercalls) that are860 Register usage for these hypercalls is identical to that of the other861 hypercalls defined in the Power Architecture Platform Reference (PAPR)868 This document only covers hypercalls currently implemented/planned871 The full specification for all hypercalls/ultracalls will eventually878 Following are the set of hypercalls needed to support Ultravisor.
24 issue hypercalls to the hypervisor whenever it needs to perform an action
39 interacting with the ACRN Hypervisor via hypercalls. HSM exports a char device
97 of the completion via hypercalls.
59 of UEFI runtime services implemented via hypercalls, see
15 Two new SMCCC compatible hypercalls are defined:
121 passing Xen hypercalls to userspace.
102 kvm/hypercalls.o/
267 perform Xen hypercalls. This driver is normally required for systems
239 and use "batched" hypercalls.
Completed in 45 milliseconds