Lines Matching refs:hypercall

944 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
945 page, and provides the starting address and size of the hypercall
966 the contents of the hypercall page automatically; hypercalls will be
974 such as intercepting the SCHEDOP_poll hypercall to accelerate PV
1791 The hcall array defines 4 instructions that make up a hypercall.
2641 The bitmap feature firmware registers exposes the hypercall services that
4327 implementing the H_RESIZE_HPT_PREPARE hypercall.
4384 H_RESIZE_HPT_COMMIT hypercall.
4669 H_GET_CPU_CHARACTERISTICS hypercall.
4733 the specified Hyper-V connection id through the SIGNAL_EVENT hypercall, without
4734 causing a user exit.  SIGNAL_EVENT hypercall with non-zero event flag number
5490   Xen guests will often use this to as a dummy hypercall to trigger
5500   hypercall.
5608   the HVMOP_set_evtchn_upcall_vector hypercall. This is typically
6263 		} hypercall;
6366 MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch
6369 If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall.
6370 Userspace can now handle the hypercall and when it's done modify the gprs as
6385 guest does a hypercall using the 'sc 1' instruction.  The 'nr' field
6386 contains the hypercall number (from the guest R3), and 'args' contains
6448 a system-level event using some architecture specific mechanism (hypercall
6681   - KVM_EXIT_XEN_HCALL -- synchronously notify user-space about Xen hypercall.
6682     Userspace is expected to place the hypercall result into the appropriate
6808 done using the hypercall instruction "sc 1".
7612 resource that is controlled with the H_SET_MODE hypercall.
7668                                     vendor's hypercall instruction for the
7671                                     hypercall instructions. Executing the
7672                                     incorrect hypercall instruction will
7752 H_RANDOM hypercall backed by a hardware random-number generator.
8022 Due to the different ABI for hypercall parameters between Hyper-V and
8023 KVM, enabling this capability effectively disables all hypercall
8024 handling by KVM (as some KVM hypercall may be mistakenly treated as TLB
8257 ioctl is available, for the guest to set its hypercall page.
8260 provided in the flags to KVM_XEN_HVM_CONFIG, without providing hypercall page
8261 contents, to request that KVM generate hypercall page content automatically
8295 specifically enabled (by the guest making the hypercall, causing the VMM
8356 Right now, the only such hypercall is KVM_HC_MAP_GPA_RANGE.