| /Linux-v5.10/arch/arm/xen/ |
| D | hypercall.S | 57 #define HYPERCALL_SIMPLE(hypercall) \ argument
58 ENTRY(HYPERVISOR_##hypercall) \
59 mov r12, #__HYPERVISOR_##hypercall; \
62 ENDPROC(HYPERVISOR_##hypercall)
70 #define HYPERCALL5(hypercall) \ argument
71 ENTRY(HYPERVISOR_##hypercall) \
74 mov r12, #__HYPERVISOR_##hypercall; \
78 ENDPROC(HYPERVISOR_##hypercall)
|
| D | Makefile | 2 obj-y := enlighten.o hypercall.o grant-table.o p2m.o mm.o
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | hypercalls.rst | 13 The hypercall number should be placed in rax and the return value will be
15 by the particular hypercall.
18 R2-R7 are used for parameters 1-6. In addition, R1 is used for hypercall
21 S390 uses diagnose instruction as hypercall (0x500) along with hypercall
28 It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.
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
43 The template for each hypercall is:
70 :Purpose: Expose hypercall availability to the guest. On x86 platforms, cpuid
73 OR KVM specific enumeration mechanism (which is this hypercall)
[all …]
|
| D | ppc-pv.rst | 35 'hypercall-instructions'. This property contains at most 4 opcodes that make
36 up the hypercall. To call a hypercall, just call these instructions.
52 r11 hypercall number 8th output value
56 Hypercall definitions are shared in generic code, so the same hypercall numbers
57 apply for x86 and powerpc alike with the exception that each KVM hypercall
75 map this shared page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE.
77 With this hypercall issued the guest always gets the magic page mapped at the
88 also define a new hypercall feature to indicate that the host can give you more
97 When mapping the magic page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE,
206 These are ePAPR compliant hypercall implementation (mentioned above). Even
[all …]
|
| D | s390-diag.rst | 77 See also the virtio standard for a discussion of this hypercall.
|
| D | api.rst | 929 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
930 page, and provides the starting address and size of the hypercall
1668 The hcall array defines 4 instructions that make up a hypercall.
3871 implementing the H_RESIZE_HPT_PREPARE hypercall.
3928 H_RESIZE_HPT_COMMIT hypercall.
4207 H_GET_CPU_CHARACTERISTICS hypercall.
4271 the specified Hyper-V connection id through the SIGNAL_EVENT hypercall, without
4272 causing a user exit. SIGNAL_EVENT hypercall with non-zero event flag number
4992 } hypercall;
4994 Unused. This was once used for 'hypercall to userspace'. To implement
[all …]
|
| /Linux-v5.10/arch/arm64/xen/ |
| D | hypercall.S | 58 #define HYPERCALL_SIMPLE(hypercall) \ argument
59 SYM_FUNC_START(HYPERVISOR_##hypercall) \
60 mov x16, #__HYPERVISOR_##hypercall; \
63 SYM_FUNC_END(HYPERVISOR_##hypercall)
|
| D | Makefile | 3 obj-y := xen-arm.o hypercall.o
|
| /Linux-v5.10/Documentation/powerpc/ |
| D | ultravisor.rst | 173 registers not needed for the hypercall then reflects the call to
174 the hypervisor for processing. The H_RANDOM hypercall is performed
323 ``H_SVM_PAGE_OUT`` hypercall to the Hypervisor. The Hypervisor will
510 processing an hypercall or interrupt that was forwarded (aka
529 When an SVM makes an hypercall or incurs some other exception, the
537 * If returning from an hypercall, register R0 contains the return
539 contain any output values of the hypercall.
548 the SVM such as processing hypercall and other exceptions. After
864 additional parameters to the hypercall, if any. On output, register
866 other output values from the hypercall.
[all …]
|
| /Linux-v5.10/Documentation/virt/kvm/arm/ |
| D | hyp-abi.rst | 59 This hypercall is not expected to return to its caller.
64 The return value of a stub hypercall is held by r0/x0, and is 0 on
65 success, and HVC_STUB_ERR on error. A stub hypercall is allowed to
68 the hypercall.
|
| D | pvtime.rst | 22 the PV_FEATURES hypercall should be probed using the SMCCC 1.1 ARCH_FEATURES
52 The structure pointed to by the PV_TIME_ST hypercall is as follows:
|
| /Linux-v5.10/drivers/xen/ |
| D | privcmd.c | 70 struct privcmd_hypercall hypercall; in privcmd_ioctl_hypercall() local
77 if (copy_from_user(&hypercall, udata, sizeof(hypercall))) in privcmd_ioctl_hypercall()
81 ret = privcmd_call(hypercall.op, in privcmd_ioctl_hypercall()
82 hypercall.arg[0], hypercall.arg[1], in privcmd_ioctl_hypercall()
83 hypercall.arg[2], hypercall.arg[3], in privcmd_ioctl_hypercall()
84 hypercall.arg[4]); in privcmd_ioctl_hypercall()
|
| /Linux-v5.10/Documentation/devicetree/bindings/arm/ |
| D | xen.txt | 12 HYPERVISOR_memory_op hypercall. The memory region is large enough to map
60 http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,platform.h.html.
|
| /Linux-v5.10/arch/powerpc/kernel/ |
| D | exceptions-64e.S | 553 EXCEPTION_STUB(0x300, hypercall)
927 START_EXCEPTION(hypercall);
|
| /Linux-v5.10/arch/x86/kvm/svm/ |
| D | svm.c | 3705 svm_patch_hypercall(struct kvm_vcpu *vcpu, unsigned char *hypercall) in svm_patch_hypercall() argument
3710 hypercall[0] = 0x0f; in svm_patch_hypercall()
3711 hypercall[1] = 0x01; in svm_patch_hypercall()
3712 hypercall[2] = 0xd9; in svm_patch_hypercall()
|
| /Linux-v5.10/tools/include/uapi/linux/ |
| D | kvm.h | 329 } hypercall; member
|
| /Linux-v5.10/include/uapi/linux/ |
| D | kvm.h | 329 } hypercall; member
|
| /Linux-v5.10/Documentation/sparc/oradax/ |
| D | oracle-dax.rst | 399 The dax submit hypercall is made directly. The flags used in the
|
| D | dax-hv-api.txt | 380 during that hypercall invocation.
1313 … be possible to stop the execution using the ccb_kill hypercall.
1321 … guest software should invoke the ccb_kill hypercall prior to assuming the request CCB will never
|
| /Linux-v5.10/arch/x86/kvm/vmx/ |
| D | vmx.c | 4921 vmx_patch_hypercall(struct kvm_vcpu *vcpu, unsigned char *hypercall) in vmx_patch_hypercall() argument
4926 hypercall[0] = 0x0f; in vmx_patch_hypercall()
4927 hypercall[1] = 0x01; in vmx_patch_hypercall()
4928 hypercall[2] = 0xc1; in vmx_patch_hypercall()
|
