Home
last modified time | relevance | path

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

12

/openbmc/linux/arch/x86/entry/syscalls/
H 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
/openbmc/linux/Documentation/virt/kvm/
H 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
/openbmc/linux/Documentation/virt/kvm/arm/
H A Dindex.rst11 hypercalls
H A Dpvtime.rst15 Two new SMCCC compatible hypercalls are defined:
/openbmc/linux/Documentation/virt/kvm/s390/
H 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
/openbmc/linux/Documentation/virt/kvm/x86/
H A Dindex.rst13 hypercalls
H 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
/openbmc/linux/arch/x86/include/asm/
H A DKbuild10 generated-y += xen-hypercalls.h
/openbmc/linux/Documentation/translations/zh_CN/virt/acrn/
H A Dintroduction.rst48 与ACRN超级管理器的hypercalls进行交互来实现管理服务。HSM向用户空间输出一个char设备接口
H A Dio-request.rst99 f. HSM将I/O请求状态更新为COMPLETE,并通过hypercalls通知超级管理器完成。
/openbmc/linux/drivers/virt/acrn/
H A DKconfig9 the ACRN Hypervisor through hypercalls. HSM will only run in
/openbmc/linux/Documentation/virt/hyperv/
H 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
/openbmc/linux/arch/arm64/kvm/
H A DMakefile13 kvm-y += arm.o mmu.o mmio.o psci.o hypercalls.o pvtime.o \
/openbmc/linux/Documentation/virt/acrn/
H A Dintroduction.rst39 interacting with the ACRN Hypervisor via hypercalls. HSM exports a char device
H A Dio-request.rst97 of the completion via hypercalls.
/openbmc/linux/Documentation/powerpc/
H 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.
H A Dpapr_hcalls.rst24 issue hypercalls to the hypervisor whenever it needs to perform an action
/openbmc/linux/Documentation/devicetree/bindings/arm/
H A Dxen.txt61 of UEFI runtime services implemented via hypercalls, see
/openbmc/qemu/docs/system/i386/
H A Dhyperv.rst238 Hyper-V specification allows to pass parameters for certain hypercalls using XMM
240 for faster hypercalls processing as KVM can avoid reading guest's memory.
243 Allow for extended GVA ranges to be passed to Hyper-V TLB flush hypercalls
250 enabled, it allows L0 (KVM) to directly handle TLB flush hypercalls from L2
H A Dxen.rst8 KVM has support for hosting Xen guests, intercepting Xen hypercalls and event
/openbmc/qemu/docs/specs/
H A Dppc-spapr-hcalls.rst17 All those hypercalls start at hcall number 0xf000 which correspond
H A Dppc-spapr-uv-hcalls.rst12 The various ultracalls/hypercalls relating to SVM mode are currently only
/openbmc/linux/arch/x86/kvm/
H A DKconfig137 passing Xen hypercalls to userspace.
/openbmc/linux/tools/testing/selftests/kvm/
H A DMakefile145 TEST_GEN_PROGS_aarch64 += aarch64/hypercalls
/openbmc/linux/arch/powerpc/kvm/
H A DKconfig141 hypercalls and page faults. The total, minimum and maximum

12