Lines Matching refs:hypercall

999 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
1000 page, and provides the starting address and size of the hypercall
1025 the contents of the hypercall page automatically; hypercalls will be
1033 such as intercepting the SCHEDOP_poll hypercall to accelerate PV
1874 The hcall array defines 4 instructions that make up a hypercall.
2701 The bitmap feature firmware registers exposes the hypercall services that
4468 implementing the H_RESIZE_HPT_PREPARE hypercall.
4525 H_RESIZE_HPT_COMMIT hypercall.
4810 H_GET_CPU_CHARACTERISTICS hypercall.
4876 the specified Hyper-V connection id through the SIGNAL_EVENT hypercall, without
4877 causing a user exit.  SIGNAL_EVENT hypercall with non-zero event flag number
5677   Xen guests will often use this to as a dummy hypercall to trigger
5687   hypercall.
5810   the HVMOP_set_evtchn_upcall_vector hypercall. This is typically
6842 		} hypercall;
6945 MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch
6948 If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall.
6949 Userspace can now handle the hypercall and when it's done modify the gprs as
6964 guest does a hypercall using the 'sc 1' instruction.  The 'nr' field
6965 contains the hypercall number (from the guest R3), and 'args' contains
7028 a system-level event using some architecture specific mechanism (hypercall
7311   - KVM_EXIT_XEN_HCALL -- synchronously notify user-space about Xen hypercall.
7312     Userspace is expected to place the hypercall result into the appropriate
7608 done using the hypercall instruction "sc 1".
7853 Due to the different ABI for hypercall parameters between Hyper-V and
7854 KVM, enabling this capability effectively disables all hypercall
7855 handling by KVM (as some KVM hypercall may be mistakenly treated as TLB
8571                                            vendor's hypercall instruction for the
8574                                            hypercall instructions. Executing the
8575                                            incorrect hypercall instruction will
8931 Userspace may fail the hypercall by setting hypercall.ret to EINVAL
8932 or may request the hypercall to be retried the next time the guest run
8933 by setting hypercall.ret to EAGAIN.
8937 Right now, the only such hypercall is KVM_HC_MAP_GPA_RANGE.
9048 H_RANDOM hypercall backed by a hardware random-number generator.
9365 ioctl is available, for the guest to set its hypercall page.
9368 provided in the flags to KVM_XEN_HVM_CONFIG, without providing hypercall page
9369 contents, to request that KVM generate hypercall page content automatically
9403 specifically enabled (by the guest making the hypercall, causing the VMM
9525 resource that is controlled with the H_SET_MODE hypercall.