Searched refs:hypercalls (Results 1 – 25 of 27) sorted by relevance
12
| /Linux-v6.6/arch/x86/entry/syscalls/ |
| D | Makefile | 60 $(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-v6.6/Documentation/virt/kvm/ |
| D | ppc-pv.rst | 29 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
|
| D | api.rst | 966 the contents of the hypercall page automatically; hypercalls will be
2653 (See Documentation/virt/kvm/arm/hypercalls.rst for more details.)
6367 hypercalls and exit with this exit struct that contains all the guest gprs.
6389 The possible hypercalls are defined in the Power Architecture Platform
6791 This capability enables interception of OSI hypercalls that otherwise would
6792 be treated as normal system calls to be injected into the guest. OSI hypercalls
6807 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
7046 This capability controls whether individual sPAPR hypercalls (hcalls)
7986 hypercalls:
8011 hypercalls:
[all …]
|
| /Linux-v6.6/Documentation/virt/kvm/arm/ |
| D | index.rst | 11 hypercalls
|
| D | pvtime.rst | 15 Two new SMCCC compatible hypercalls are defined:
|
| /Linux-v6.6/Documentation/virt/kvm/x86/ |
| D | index.rst | 13 hypercalls
|
| D | hypercalls.rst | 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 hypercall
71 used to enumerate which hypercalls are available. On PPC, either
|
| /Linux-v6.6/Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 7 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
8 native hypercalls and for selected hypercalls found on other s390
|
| /Linux-v6.6/arch/x86/include/asm/ |
| D | Kbuild | 10 generated-y += xen-hypercalls.h
|
| D | kvm_host.h | 1514 u64 hypercalls; member
|
| /Linux-v6.6/Documentation/translations/zh_CN/virt/acrn/ |
| D | introduction.rst | 48 与ACRN超级管理器的hypercalls进行交互来实现管理服务。HSM向用户空间输出一个char设备接口
|
| D | io-request.rst | 99 f. HSM将I/O请求状态更新为COMPLETE，并通过hypercalls通知超级管理器完成。
|
| /Linux-v6.6/drivers/virt/acrn/ |
| D | Kconfig | 9 the ACRN Hypervisor through hypercalls. HSM will only run in
|
| /Linux-v6.6/Documentation/virt/hyperv/ |
| D | overview.rst | 28 * 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-v6.6/arch/arm64/kvm/ |
| D | Makefile | 13 kvm-y += arm.o mmu.o mmio.o psci.o hypercalls.o pvtime.o \
|
| /Linux-v6.6/Documentation/virt/acrn/ |
| D | introduction.rst | 39 interacting with the ACRN Hypervisor via hypercalls. HSM exports a char device
|
| D | io-request.rst | 97 of the completion via hypercalls.
|
| /Linux-v6.6/Documentation/powerpc/ |
| D | ultravisor.rst | 42 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.
|
| D | papr_hcalls.rst | 24 issue hypercalls to the hypervisor whenever it needs to perform an action
|
| /Linux-v6.6/Documentation/devicetree/bindings/arm/ |
| D | xen.txt | 61 of UEFI runtime services implemented via hypercalls, see
|
| /Linux-v6.6/arch/x86/kvm/ |
| D | Kconfig | 137 passing Xen hypercalls to userspace.
|
| /Linux-v6.6/tools/testing/selftests/kvm/ |
| D | Makefile | 145 TEST_GEN_PROGS_aarch64 += aarch64/hypercalls
|
| /Linux-v6.6/arch/powerpc/kvm/ |
| D | Kconfig | 141 hypercalls and page faults. The total, minimum and maximum
|
| /Linux-v6.6/drivers/xen/ |
| D | Kconfig | 267 perform Xen hypercalls. This driver is normally required for systems
|
| /Linux-v6.6/Documentation/arch/sparc/oradax/ |
| D | oracle-dax.rst | 265 can make hypercalls directly while the user code must use wrappers
|
12
