Home
last modified time | relevance | path

Searched refs:hypercall (Results 1 – 25 of 43) sorted by relevance

12

/linux/arch/arm/xen/
H A Dhypercall.S2 * hypercall.S
4 * Xen hypercall wrappers
34 * The Xen hypercall calling convention is very similar to the ARM
41 * The hypercall number is passed in r12.
46 * hypercall tag.
57 #define HYPERCALL_SIMPLE(hypercall) \ argument
58 ENTRY(HYPERVISOR_##hypercall) \
59 mov r12, #__HYPERVISOR_##hypercall; \
62 ENDPROC(HYPERVISOR_##hypercall)
70 #define HYPERCALL5(hypercall) \ argument
[all...]
H A DMakefile2 obj-y := enlighten.o hypercall.o grant-table.o p2m.o mm.o
/linux/Documentation/virt/kvm/x86/
H A Dhypercalls.rst13 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 availabilit
[all...]
H A Dcpuid.rst100 using the map gpa range hypercall
/linux/arch/arm64/xen/
H A Dhypercall.S2 * hypercall.S
4 * Xen hypercall wrappers
34 * The Xen hypercall calling convention is very similar to the procedure
39 * The hypercall number is passed in x16.
44 * hypercall tag.
58 #define HYPERCALL_SIMPLE(hypercall) \ argument
59 SYM_FUNC_START(HYPERVISOR_##hypercall) \
60 mov x16, #__HYPERVISOR_##hypercall; \
63 SYM_FUNC_END(HYPERVISOR_##hypercall)
H A DMakefile3 obj-y := xen-arm.o hypercall.o
/linux/Documentation/virt/kvm/loongarch/
H A Dhypercalls.rst7 KVM hypercalls use the HVCL instruction with code 0x100 and the hypercall
30 KVM hypercall ABI
33 The KVM hypercall ABI is simple, with one scratch register a0 (v0) and at most
36 remain unmodified during a hypercall.
66 The template for each hypercall is as follows:
81 The hypercall lets a guest send multiple IPIs (Inter-Process Interrupts) with
82 at most 128 destinations per hypercall. The destinations are represented in a
/linux/Documentation/virt/kvm/
H A Dppc-pv.rst35 '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_PAG
[all...]
/linux/tools/testing/selftests/kvm/x86/
H A Dprivate_mem_conversions_test.c53 * Execute KVM hypercall to map/unmap gpa range which will cause userspace exit
292 uint64_t gpa = run->hypercall.args[0]; in handle_exit_hypercall()
293 uint64_t size = run->hypercall.args[1] * PAGE_SIZE; in handle_exit_hypercall()
294 bool set_attributes = run->hypercall.args[2] & MAP_GPA_SET_ATTRIBUTES; in handle_exit_hypercall()
295 bool map_shared = run->hypercall.args[2] & MAP_GPA_SHARED; in handle_exit_hypercall()
296 bool do_fallocate = run->hypercall.args[2] & MAP_GPA_DO_FALLOCATE; in handle_exit_hypercall()
299 TEST_ASSERT(run->hypercall.nr == KVM_HC_MAP_GPA_RANGE, in handle_exit_hypercall()
301 KVM_HC_MAP_GPA_RANGE, run->hypercall.nr); in handle_exit_hypercall()
309 run->hypercall.ret = 0; in handle_exit_hypercall()
/linux/tools/testing/selftests/kvm/arm64/
H A Dsmccc_filter.c214 TEST_ASSERT(run->hypercall.nr == func_id, in expect_call_fwd_to_user()
215 "Unexpected SMCCC function: %llu", run->hypercall.nr); in expect_call_fwd_to_user()
218 TEST_ASSERT(run->hypercall.flags & KVM_HYPERCALL_EXIT_SMC, in expect_call_fwd_to_user()
221 TEST_ASSERT(!(run->hypercall.flags & KVM_HYPERCALL_EXIT_SMC), in expect_call_fwd_to_user()
/linux/Documentation/arch/powerpc/
H A Dultravisor.rst173 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/arch/loongarch/kvm/
H A Dexit.c723 kvm_write_reg(vcpu, LOONGARCH_GPR_A0, run->hypercall.ret); in kvm_complete_user_service()
896 vcpu->run->hypercall.nr = KVM_HCALL_USER_SERVICE; in kvm_handle_hypercall()
897 vcpu->run->hypercall.args[0] = kvm_read_reg(vcpu, LOONGARCH_GPR_A0); in kvm_handle_hypercall()
898 vcpu->run->hypercall.args[1] = kvm_read_reg(vcpu, LOONGARCH_GPR_A1); in kvm_handle_hypercall()
899 vcpu->run->hypercall.args[2] = kvm_read_reg(vcpu, LOONGARCH_GPR_A2); in kvm_handle_hypercall()
900 vcpu->run->hypercall.args[3] = kvm_read_reg(vcpu, LOONGARCH_GPR_A3); in kvm_handle_hypercall()
901 vcpu->run->hypercall.args[4] = kvm_read_reg(vcpu, LOONGARCH_GPR_A4); in kvm_handle_hypercall()
902 vcpu->run->hypercall.args[5] = kvm_read_reg(vcpu, LOONGARCH_GPR_A5); in kvm_handle_hypercall()
903 vcpu->run->hypercall.flags = 0; in kvm_handle_hypercall()
907 vcpu->run->hypercall in kvm_handle_hypercall()
[all...]
/linux/Documentation/virt/kvm/arm/
H A Dhyp-abi.rst59 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.
H A Dfw-pseudo-registers.rst7 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
H A Dpvtime.rst22 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:
H A Dptp_kvm.rst8 host to the guest using a KVM-specific hypercall.
/linux/arch/x86/hyperv/
H A Divm.c64 } hypercall; member
94 hv_ghcb->hypercall.outputgpa = (u64)output; in hv_ghcb_hypercall()
95 hv_ghcb->hypercall.hypercallinput.asuint64 = 0; in hv_ghcb_hypercall()
96 hv_ghcb->hypercall.hypercallinput.callcode = control; in hv_ghcb_hypercall()
99 memcpy(hv_ghcb->hypercall.hypercalldata, input, input_size); in hv_ghcb_hypercall()
107 status = hv_ghcb->hypercall.hypercalloutput.callstatus; in hv_ghcb_hypercall()
/linux/Documentation/devicetree/bindings/arm/
H A Dxen.txt12 hypercall.
62 http://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,platform.h.html.
/linux/drivers/xen/
H A Dprivcmd.c36 #include <asm/xen/hypercall.h>
55 MODULE_DESCRIPTION("Xen hypercall passthrough driver");
63 "Maximum number of buffers per dm_op hypercall");
69 "Maximum size of a dm_op hypercall buffer");
83 struct privcmd_hypercall hypercall; in privcmd_ioctl_hypercall() local
90 if (copy_from_user(&hypercall, udata, sizeof(hypercall))) in privcmd_ioctl_hypercall()
94 ret = privcmd_call(hypercall.op, in privcmd_ioctl_hypercall()
95 hypercall.arg[0], hypercall in privcmd_ioctl_hypercall()
[all...]
/linux/Documentation/translations/zh_CN/virt/acrn/
H A Dintroduction.rst40 +---------------------hypercall----------------------------------------+
/linux/Documentation/virt/acrn/
H A Dintroduction.rst29 +---------------------hypercall----------------------------------------+
/linux/arch/powerpc/platforms/ps3/
H A DKconfig91 bool "PS3 Verbose LV1 hypercall results" if PS3_ADVANCED
94 Enables more verbose log messages for LV1 hypercall results.
/linux/arch/arm64/kvm/
H A Dhypercalls.c259 run->hypercall = (typeof(run->hypercall)) { in kvm_prepare_hypercall_exit()
455 * As for the hypercall discovery, we pretend we in get_kernel_wa_level()
/linux/arch/x86/kvm/svm/
H A Dsev.c3648 if (vcpu->run->hypercall.ret) in snp_complete_psc_msr()
3673 vcpu->run->hypercall.nr = KVM_HC_MAP_GPA_RANGE; in snp_begin_psc_msr()
3676 * assumed that vcpu->run->hypercall.ret is never changed by KVM and thus that in snp_begin_psc_msr()
3678 * vcpu->run->hypercall.ret, ensuring that it is zero to not break QEMU. in snp_begin_psc_msr()
3680 vcpu->run->hypercall.ret = 0; in snp_begin_psc_msr()
3681 vcpu->run->hypercall.args[0] = gpa; in snp_begin_psc_msr()
3682 vcpu->run->hypercall.args[1] = 1; in snp_begin_psc_msr()
3683 vcpu->run->hypercall.args[2] = (op == SNP_PAGE_STATE_PRIVATE) in snp_begin_psc_msr()
3686 vcpu->run->hypercall.args[2] |= KVM_MAP_GPA_RANGE_PAGE_SZ_4K; in snp_begin_psc_msr()
3742 if (vcpu->run->hypercall in snp_complete_one_psc()
[all...]
/linux/arch/x86/kvm/vmx/
H A Dtdx.c637 * Instead, guest uses MMIO hypercall. For unmodified device driver, in tdx_vm_init()
639 * instruction into MMIO hypercall. in tdx_vm_init()
1129 tdvmcall_set_return_code(vcpu, vcpu->run->hypercall.ret); in complete_hypercall_exit()
1156 if (vcpu->run->hypercall.ret) { in tdx_complete_vmcall_map_gpa()
1190 tdx->vcpu.run->hypercall.nr = KVM_HC_MAP_GPA_RANGE; in __tdx_map_gpa()
1193 * assumed that vcpu->run->hypercall.ret is never changed by KVM and thus that in __tdx_map_gpa()
1195 * vcpu->run->hypercall.ret, ensuring that it is zero to not break QEMU. in __tdx_map_gpa()
1197 tdx->vcpu.run->hypercall.ret = 0; in __tdx_map_gpa()
1198 tdx->vcpu.run->hypercall.args[0] = gpa & ~gfn_to_gpa(kvm_gfn_direct_bits(tdx->vcpu.kvm)); in __tdx_map_gpa()
1199 tdx->vcpu.run->hypercall in __tdx_map_gpa()
[all...]

12