Lines Matching refs:hypercall

953 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;
5511 Unused.  This was once used for 'hypercall to userspace'.  To implement
5586 MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch
5589 If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall.
5590 Userspace can now handle the hypercall and when it's done modify the gprs as
5605 guest does a hypercall using the 'sc 1' instruction.  The 'nr' field
5606 contains the hypercall number (from the guest R3), and 'args' contains
5664 a system-level event using some architecture specific mechanism (hypercall
5847   - KVM_EXIT_XEN_HCALL -- synchronously notify user-space about Xen hypercall.
5848     Userspace is expected to place the hypercall result into the appropriate
5939 done using the hypercall instruction "sc 1".
6722 H_RANDOM hypercall backed by a hardware random-number generator.
6992 Due to the different ABI for hypercall parameters between Hyper-V and
6993 KVM, enabling this capability effectively disables all hypercall
6994 handling by KVM (as some KVM hypercall may be mistakenly treated as TLB
7187 ioctl is available, for the guest to set its hypercall page.
7190 provided in the flags to KVM_XEN_HVM_CONFIG, without providing hypercall page
7191 contents, to request that KVM generate hypercall page content automatically
7262 Right now, the only such hypercall is KVM_HC_MAP_GPA_RANGE.