Home
last modified time | relevance | path

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

12

/Linux-v5.15/arch/arm/xen/
Dhypercall.S57 #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)
DMakefile2 obj-y := enlighten.o hypercall.o grant-table.o p2m.o mm.o
/Linux-v5.15/Documentation/virt/kvm/
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 availability to the guest. On x86 platforms, cpuid
73 OR KVM specific enumeration mechanism (which is this hypercall)
[all …]
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_PAGE,
206 These are ePAPR compliant hypercall implementation (mentioned above). Even
[all …]
Dcpuid.rst100 using the map gpa range hypercall
Ds390-diag.rst77 See also the virtio standard for a discussion of this hypercall.
Dapi.rst953 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
954 page, and provides the starting address and size of the hypercall
973 This requests KVM to generate the contents of the hypercall page
1704 The hcall array defines 4 instructions that make up a hypercall.
3963 implementing the H_RESIZE_HPT_PREPARE hypercall.
4020 H_RESIZE_HPT_COMMIT hypercall.
4299 H_GET_CPU_CHARACTERISTICS hypercall.
4363 the specified Hyper-V connection id through the SIGNAL_EVENT hypercall, without
4364 causing a user exit. SIGNAL_EVENT hypercall with non-zero event flag number
5509 } hypercall;
[all …]
Dmsr.rst390 ``KVM_HC_MAP_GPA_RANGE`` hypercall, it can set bit 0 in this MSR to
/Linux-v5.15/arch/arm64/xen/
Dhypercall.S58 #define HYPERCALL_SIMPLE(hypercall) \ argument
59 SYM_FUNC_START(HYPERVISOR_##hypercall) \
60 mov x16, #__HYPERVISOR_##hypercall; \
63 SYM_FUNC_END(HYPERVISOR_##hypercall)
DMakefile3 obj-y := xen-arm.o hypercall.o
/Linux-v5.15/Documentation/powerpc/
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-v5.15/Documentation/virt/kvm/arm/
Dptp_kvm.rst8 host to the guest using a KVM-specific hypercall.
12 This hypercall uses the SMC32/HVC32 calling convention:
Dhyp-abi.rst59 This hypercall is not expected to return to its caller.
73 The return value of a stub hypercall is held by r0/x0, and is 0 on
74 success, and HVC_STUB_ERR on error. A stub hypercall is allowed to
77 the hypercall.
Dpvtime.rst22 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-v5.15/drivers/xen/
Dprivcmd.c70 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.15/Documentation/devicetree/bindings/arm/
Dxen.txt12 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.15/Documentation/translations/zh_CN/virt/acrn/
Dintroduction.rst40 +---------------------hypercall----------------------------------------+
/Linux-v5.15/Documentation/virt/acrn/
Dintroduction.rst29 +---------------------hypercall----------------------------------------+
/Linux-v5.15/arch/powerpc/platforms/ps3/
DKconfig90 bool "PS3 Verbose LV1 hypercall results" if PS3_ADVANCED
93 Enables more verbose log mesages for LV1 hypercall results.
/Linux-v5.15/tools/testing/selftests/kvm/x86_64/
Dhyperv_features.c52 static inline u64 hypercall(u64 control, vm_vaddr_t input_address, in hypercall() function
142 res = hypercall(hcall->control, input, output); in guest_hcall()
/Linux-v5.15/arch/x86/kvm/
DKconfig117 bool "Support for Xen hypercall interface"
/Linux-v5.15/arch/powerpc/kernel/
Dexceptions-64e.S513 EXCEPTION_STUB(0x300, hypercall)
878 START_EXCEPTION(hypercall);
/Linux-v5.15/arch/x86/kvm/svm/
Dsvm.c3944 svm_patch_hypercall(struct kvm_vcpu *vcpu, unsigned char *hypercall) in svm_patch_hypercall() argument
3949 hypercall[0] = 0x0f; in svm_patch_hypercall()
3950 hypercall[1] = 0x01; in svm_patch_hypercall()
3951 hypercall[2] = 0xd9; in svm_patch_hypercall()
/Linux-v5.15/tools/include/uapi/linux/
Dkvm.h351 } hypercall; member
/Linux-v5.15/include/uapi/linux/
Dkvm.h351 } hypercall; member

12