/linux-6.3-rc2/arch/arm/xen/ |
A 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)
|
A D | Makefile | 2 obj-y := enlighten.o hypercall.o grant-table.o p2m.o mm.o
|
/linux-6.3-rc2/Documentation/virt/kvm/x86/ |
A D | hypercalls.rst | 13 The hypercall number should be placed in rax and the return value will be 15 by the particular hypercall. 21 S390 uses diagnose instruction as hypercall (0x500) along with hypercall 43 The template for each hypercall is: 73 OR KVM specific enumeration mechanism (which is this hypercall) 84 through memory using this hypercall. 100 is used in the hypercall for future use. 133 The hypercall lets a guest compute a precise timestamp across 152 The hypercall lets a guest send multicast IPIs, with at most 128 153 128 destinations per hypercall in 64-bit mode and 64 vCPUs per [all …]
|
A D | cpuid.rst | 100 using the map gpa range hypercall
|
/linux-6.3-rc2/arch/arm64/xen/ |
A 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)
|
A D | Makefile | 3 obj-y := xen-arm.o hypercall.o
|
/linux-6.3-rc2/arch/x86/hyperv/ |
A 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.3-rc2/Documentation/virt/kvm/ |
A 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 …]
|
A D | api.rst | 945 page, and provides the starting address and size of the hypercall 974 such as intercepting the SCHEDOP_poll hypercall to accelerate PV 4325 implementing the H_RESIZE_HPT_PREPARE hypercall. 4382 H_RESIZE_HPT_COMMIT hypercall. 4667 H_GET_CPU_CHARACTERISTICS hypercall. 5498 hypercall. 6223 } hypercall; 6742 done using the hypercall instruction "sc 1". 7545 resource that is controlled with the H_SET_MODE hypercall. 8190 ioctl is available, for the guest to set its hypercall page. [all …]
|
/linux-6.3-rc2/Documentation/powerpc/ |
A D | ultravisor.rst | 539 contain any output values of the hypercall. 866 other output values from the hypercall. 890 uint64_t hypercall(const uint64_t H_SVM_INIT_START) 907 completed, Ultravisor issues the H_SVM_INIT_DONE hypercall. 926 uint64_t hypercall(const uint64_t H_SVM_INIT_DONE) 936 hypercall). 964 uint64_t hypercall(const uint64_t H_SVM_INIT_ABORT) 977 H_SVM_INIT_DONE hypercall was successful). 1024 uint64_t hypercall(const uint64_t H_SVM_PAGE_IN, 1083 uint64_t hypercall(const uint64_t H_SVM_PAGE_OUT, [all …]
|
/linux-6.3-rc2/Documentation/virt/kvm/arm/ |
A D | ptp_kvm.rst | 8 host to the guest using a KVM-specific hypercall. 12 This hypercall uses the SMC32/HVC32 calling convention:
|
A 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.
|
A 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
|
A D | pvtime.rst | 22 the PV_TIME_FEATURES hypercall should be probed using the SMCCC 1.1 54 The structure pointed to by the PV_TIME_ST hypercall is as follows:
|
/linux-6.3-rc2/drivers/xen/ |
A 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()
|
A D | Kconfig | 262 tristate "Xen hypercall passthrough driver" 266 The hypercall passthrough driver allows privileged user programs to
|
/linux-6.3-rc2/Documentation/devicetree/bindings/arm/ |
A D | xen.txt | 12 hypercall. 62 http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,platform.h.html.
|
/linux-6.3-rc2/Documentation/translations/zh_CN/virt/acrn/ |
A D | introduction.rst | 40 +---------------------hypercall----------------------------------------+
|
/linux-6.3-rc2/Documentation/virt/acrn/ |
A D | introduction.rst | 29 +---------------------hypercall----------------------------------------+
|
/linux-6.3-rc2/Documentation/x86/ |
A 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.3-rc2/arch/powerpc/platforms/ps3/ |
A D | Kconfig | 90 bool "PS3 Verbose LV1 hypercall results" if PS3_ADVANCED 93 Enables more verbose log messages for LV1 hypercall results.
|
/linux-6.3-rc2/arch/x86/kvm/ |
A D | Kconfig | 134 bool "Support for Xen hypercall interface"
|
/linux-6.3-rc2/Documentation/virt/kvm/s390/ |
A D | s390-diag.rst | 77 See also the virtio standard for a discussion of this hypercall.
|
/linux-6.3-rc2/arch/powerpc/kernel/ |
A D | exceptions-64e.S | 493 EXCEPTION_STUB(0x300, hypercall) 865 START_EXCEPTION(hypercall);
|
/linux-6.3-rc2/arch/x86/kvm/svm/ |
A D | svm.c | 4092 svm_patch_hypercall(struct kvm_vcpu *vcpu, unsigned char *hypercall) in svm_patch_hypercall() argument 4097 hypercall[0] = 0x0f; in svm_patch_hypercall() 4098 hypercall[1] = 0x01; in svm_patch_hypercall() 4099 hypercall[2] = 0xd9; in svm_patch_hypercall()
|