Home
last modified time | relevance | path

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

12

/linux-6.15/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-6.15/Documentation/virt/kvm/arm/
H A Dhypercalls.rst4 KVM/arm64-specific hypercalls exposed to guests
7 This file documents the KVM/arm64-specific hypercalls which may be
8 exposed by KVM/arm64 to guest operating systems. These hypercalls are
14 All KVM/arm64-specific hypercalls are allocated within the "Vendor
18 order to determine that the KVM/arm64-specific hypercalls are available.
23 Provides a discovery mechanism for other KVM/arm64 hypercalls.
H A Dindex.rst12 hypercalls
H A Dpvtime.rst15 Two new SMCCC compatible hypercalls are defined:
/linux-6.15/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-6.15/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
/linux-6.15/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-6.15/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-6.15/arch/x86/include/asm/
H A DKbuild10 generated-y += xen-hypercalls.h
/linux-6.15/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-6.15/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
/linux-6.15/drivers/virt/acrn/
H A DKconfig9 the ACRN Hypervisor through hypercalls. HSM will only run in
/linux-6.15/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
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.
/linux-6.15/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-6.15/arch/arm64/kvm/
H A DMakefile16 kvm-y += arm.o mmu.o mmio.o psci.o hypercalls.o pvtime.o \
/linux-6.15/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-6.15/Documentation/devicetree/bindings/arm/
H A Dxen.txt61 of UEFI runtime services implemented via hypercalls, see
/linux-6.15/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-6.15/arch/x86/kvm/
H A DKconfig187 passing Xen hypercalls to userspace.
/linux-6.15/tools/testing/selftests/kvm/
H A DMakefile.kvm150 TEST_GEN_PROGS_arm64 += arm64/hypercalls

12