| /Linux-v4.19/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 | 1 obj-y := enlighten.o hypercall.o grant-table.o p2m.o mm.o
|
| /Linux-v4.19/Documentation/virtual/kvm/ |
| D | hypercalls.txt | 9 The hypercall number should be placed in rax and the return value will be
11 by the particular hypercall.
14 R2-R7 are used for parameters 1-6. In addition, R1 is used for hypercall
17 S390 uses diagnose instruction as hypercall (0x500) along with hypercall
24 It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.
27 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
32 KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall
38 The template for each hypercall is:
62 Purpose: Expose hypercall availability to the guest. On x86 platforms, cpuid
65 mechanism (which is this hypercall) can be used.
[all …]
|
| D | ppc-pv.txt | 32 'hypercall-instructions'. This property contains at most 4 opcodes that make
33 up the hypercall. To call a hypercall, just call these instructions.
48 r11 hypercall number 8th output value
51 Hypercall definitions are shared in generic code, so the same hypercall numbers
52 apply for x86 and powerpc alike with the exception that each KVM hypercall
68 map this shared page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE.
70 With this hypercall issued the guest always gets the magic page mapped at the
81 also define a new hypercall feature to indicate that the host can give you more
90 When mapping the magic page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE,
196 These are ePAPR compliant hypercall implementation (mentioned above). Even
[all …]
|
| D | 00-INDEX | 31 - Diagnose hypercall description (for IBM S/390)
|
| D | s390-diag.txt | 73 See also the virtio standard for a discussion of this hypercall.
|
| D | api.txt | 768 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
769 page, and provides the starting address and size of the hypercall
1399 The hcall array defines 4 instructions that make up a hypercall.
3220 implementing the H_RESIZE_HPT_PREPARE hypercall.
3273 H_RESIZE_HPT_COMMIT hypercall.
3538 H_GET_CPU_CHARACTERISTICS hypercall.
3598 the specified Hyper-V connection id through the SIGNAL_EVENT hypercall, without
3599 causing a user exit. SIGNAL_EVENT hypercall with non-zero event flag number
3827 } hypercall;
3829 Unused. This was once used for 'hypercall to userspace'. To implement
[all …]
|
| /Linux-v4.19/arch/arm64/xen/ |
| D | hypercall.S | 58 #define HYPERCALL_SIMPLE(hypercall) \ argument
59 ENTRY(HYPERVISOR_##hypercall) \
60 mov x16, #__HYPERVISOR_##hypercall; \
63 ENDPROC(HYPERVISOR_##hypercall)
|
| D | Makefile | 2 obj-y := xen-arm.o hypercall.o
|
| /Linux-v4.19/Documentation/virtual/kvm/arm/ |
| D | hyp-abi.txt | 44 hypercall is not expected to return to its caller.
49 The return value of a stub hypercall is held by r0/x0, and is 0 on
50 success, and HVC_STUB_ERR on error. A stub hypercall is allowed to
53 the hypercall.
|
| /Linux-v4.19/drivers/xen/ |
| D | privcmd.c | 72 struct privcmd_hypercall hypercall; in privcmd_ioctl_hypercall() local
79 if (copy_from_user(&hypercall, udata, sizeof(hypercall))) in privcmd_ioctl_hypercall()
83 ret = privcmd_call(hypercall.op, in privcmd_ioctl_hypercall()
84 hypercall.arg[0], hypercall.arg[1], in privcmd_ioctl_hypercall()
85 hypercall.arg[2], hypercall.arg[3], in privcmd_ioctl_hypercall()
86 hypercall.arg[4]); in privcmd_ioctl_hypercall()
|
| /Linux-v4.19/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-v4.19/arch/arm/kvm/ |
| D | init.S | 66 @ Check for a stub hypercall
|
| /Linux-v4.19/arch/powerpc/kernel/ |
| D | exceptions-64e.S | 542 EXCEPTION_STUB(0x300, hypercall)
912 START_EXCEPTION(hypercall);
|
| /Linux-v4.19/tools/include/uapi/linux/ |
| D | kvm.h | 311 } hypercall; member
|
| /Linux-v4.19/include/uapi/linux/ |
| D | kvm.h | 311 } hypercall; member
|
| /Linux-v4.19/Documentation/sparc/oradax/ |
| D | oracle-dax.txt | 391 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-v4.19/arch/x86/kvm/ |
| D | svm.c | 5804 svm_patch_hypercall(struct kvm_vcpu *vcpu, unsigned char *hypercall) in svm_patch_hypercall() argument
5809 hypercall[0] = 0x0f; in svm_patch_hypercall()
5810 hypercall[1] = 0x01; in svm_patch_hypercall()
5811 hypercall[2] = 0xd9; in svm_patch_hypercall()
|
| D | vmx.c | 7179 vmx_patch_hypercall(struct kvm_vcpu *vcpu, unsigned char *hypercall) in vmx_patch_hypercall() argument
7184 hypercall[0] = 0x0f; in vmx_patch_hypercall()
7185 hypercall[1] = 0x01; in vmx_patch_hypercall()
7186 hypercall[2] = 0xc1; in vmx_patch_hypercall()
|
