Home
last modified time | relevance | path

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

12

/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
/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
H A Dapi.rst1023 the contents of the hypercall page automatically; hypercalls will be
2711 (See Documentation/virt/kvm/arm/hypercalls.rst for more details.)
6854 hypercalls and exit with this exit struct that contains all the guest gprs.
6876 The possible hypercalls are defined in the Power Architecture Platform
7499 This capability enables interception of OSI hypercalls that otherwise would
7500 be treated as normal system calls to be injected into the guest. OSI hypercalls
7515 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
7760 hypercalls are handled by Level 0 hypervisor (Hyper-V) bypassing KVM.
7764 flush hypercalls by Hyper-V) so userspace should disable KVM identification
7766 thinks it's running on Hyper-V and only use Hyper-V hypercalls.
[all …]
/linux/drivers/virt/coco/pkvm-guest/
H A DKconfig6 are isolated from the host and must issue hypercalls to enable
8 support for probing and issuing these hypercalls.
/linux/Documentation/virt/kvm/loongarch/
H A Dindex.rst10 hypercalls.rst
H A Dhypercalls.rst7 KVM hypercalls use the HVCL instruction with code 0x100 and the hypercall
28 capable KVM, you may now use hypercalls as described below.
/linux/Documentation/virt/kvm/arm/
H A Dindex.rst12 hypercalls
H A Dpvtime.rst15 Two new SMCCC compatible hypercalls are defined:
/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
/linux/arch/x86/include/asm/
H A DKbuild10 generated-y += xen-hypercalls.h
/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通知超级管理器完成。
/linux/drivers/virt/acrn/
H A DKconfig9 the ACRN Hypervisor through hypercalls. HSM will only run in
/linux/Documentation/arch/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.
/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.
/linux/arch/arm64/kvm/
H A DMakefile16 kvm-y += arm.o mmu.o mmio.o psci.o hypercalls.o pvtime.o \
/linux/Documentation/devicetree/bindings/arm/
H A Dxen.txt61 of UEFI runtime services implemented via hypercalls, see
/linux/Documentation/virt/hyperv/
H A Dcoco.rst160 When in fully-enlightened mode, hypercalls made by the Linux guest are routed
162 normal hypercalls trap to the paravisor first, which may in turn invoke the
164 hypercalls made by the Linux guest must always be routed directly to the
233 "use_calls" flag indicating to use hypercalls.
361 SIEFP, as well as hypercalls like HvPostMessage and HvSignalEvent). If the
/linux/drivers/hv/
H A DKconfig106 allow userspace to make direct hypercalls. This also allows to map VTL0's address
/linux/Documentation/security/
H A Dsnp-tdx-threat-model.rst195 hypercalls (towards Host-side VMM), access to shared memory pages,
197 well as CoCo technology-specific hypercalls, if present. Additionally, the
/linux/arch/x86/kvm/
H A DKconfig212 passing Xen hypercalls to userspace.
/linux/arch/powerpc/kvm/
H A DKconfig136 hypercalls and page faults. The total, minimum and maximum
/linux/tools/testing/selftests/kvm/
H A DMakefile.kvm169 TEST_GEN_PROGS_arm64 += arm64/hypercalls

12