| /linux-6.1.9/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-6.1.9/Documentation/virt/kvm/x86/ |
| 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 | cpuid.rst | 100 using the map gpa range hypercall
|
| /linux-6.1.9/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-6.1.9/arch/x86/hyperv/ |
| D | ivm.c | 53 } hypercall; member
81 hv_ghcb->hypercall.outputgpa = (u64)output; in hv_ghcb_hypercall()
82 hv_ghcb->hypercall.hypercallinput.asuint64 = 0; in hv_ghcb_hypercall()
83 hv_ghcb->hypercall.hypercallinput.callcode = control; in hv_ghcb_hypercall()
86 memcpy(hv_ghcb->hypercall.hypercalldata, input, input_size); in hv_ghcb_hypercall()
94 status = hv_ghcb->hypercall.hypercalloutput.callstatus; in hv_ghcb_hypercall()
|
| /linux-6.1.9/Documentation/virt/kvm/ |
| 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 | api.rst | 967 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
968 page, and provides the starting address and size of the hypercall
989 the contents of the hypercall page automatically; hypercalls will be
997 such as intercepting the SCHEDOP_poll hypercall to accelerate PV
1810 The hcall array defines 4 instructions that make up a hypercall.
2658 The bitmap feature firmware registers exposes the hypercall services that
4329 implementing the H_RESIZE_HPT_PREPARE hypercall.
4386 H_RESIZE_HPT_COMMIT hypercall.
4665 H_GET_CPU_CHARACTERISTICS hypercall.
4729 the specified Hyper-V connection id through the SIGNAL_EVENT hypercall, without
[all …]
|
| /linux-6.1.9/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-6.1.9/Documentation/virt/kvm/arm/ |
| D | ptp_kvm.rst | 8 host to the guest using a KVM-specific hypercall.
12 This hypercall uses the SMC32/HVC32 calling convention:
|
| D | hyp-abi.rst | 59 This hypercall is not expected to return to its caller.
74 The return value of a stub hypercall is held by r0/x0, and is 0 on
75 success, and HVC_STUB_ERR on error. A stub hypercall is allowed to
78 the hypercall.
|
| D | hypercalls.rst | 7 KVM handles the hypercall services as requested by the guests. New hypercall
13 is tied to a particular version of a hypercall service, or if a migration
82 hypercall services in the form of a feature-bitmap to the userspace. This
89 hypercall services via GET_ONE_REG. The user-space can write-back the
|
| D | pvtime.rst | 22 the PV_TIME_FEATURES hypercall should be probed using the SMCCC 1.1
52 The structure pointed to by the PV_TIME_ST hypercall is as follows:
|
| /linux-6.1.9/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()
|
| D | Kconfig | 262 tristate "Xen hypercall passthrough driver"
266 The hypercall passthrough driver allows privileged user programs to
|
| /linux-6.1.9/Documentation/devicetree/bindings/arm/ |
| D | xen.txt | 12 hypercall.
62 http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,platform.h.html.
|
| /linux-6.1.9/Documentation/translations/zh_CN/virt/acrn/ |
| D | introduction.rst | 40 +---------------------hypercall----------------------------------------+
|
| /linux-6.1.9/Documentation/x86/ |
| D | tdx.rst | 19 TDX includes new hypercall-like mechanisms for communicating from the
65 hypercall but it is unlikely to succeed.
68 can make a hypercall to the hypervisor to handle the #VE.
93 value with a hypercall.
|
| /linux-6.1.9/Documentation/virt/acrn/ |
| D | introduction.rst | 29 +---------------------hypercall----------------------------------------+
|
| /linux-6.1.9/arch/powerpc/platforms/ps3/ |
| D | Kconfig | 90 bool "PS3 Verbose LV1 hypercall results" if PS3_ADVANCED
93 Enables more verbose log messages for LV1 hypercall results.
|
| /linux-6.1.9/tools/testing/selftests/kvm/x86_64/ |
| D | hyperv_features.c | 18 static inline uint8_t hypercall(u64 control, vm_vaddr_t input_address, in hypercall() function
84 vector = hypercall(hcall->control, input, output, &res); in guest_hcall()
|
| /linux-6.1.9/arch/x86/kvm/ |
| D | Kconfig | 122 bool "Support for Xen hypercall interface"
|
| /linux-6.1.9/Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 77 See also the virtio standard for a discussion of this hypercall.
|
| /linux-6.1.9/arch/powerpc/kernel/ |
| D | exceptions-64e.S | 493 EXCEPTION_STUB(0x300, hypercall)
865 START_EXCEPTION(hypercall);
|