| /linux/tools/testing/selftests/kvm/x86_64/ |
| H A D | hyperv_features.c | |
| H A D | xen_vmcall_test.c | |
| H A D | hyperv_extended_hypercalls.c | |
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-pfo-nx-crypto | 15 only errors counted here are those returned from the hcall, H_COP_OP.
18 The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
19 recorded here (the hcall will retry until -EBUSY goes away).
23 hcall.
|
| H A D | sysfs-bus-papr-pmem | 9 response to H_SCM_HEALTH hcall. The details of the bit
10 flags returned in response to this hcall is available
|
| /linux/Documentation/arch/powerpc/ |
| H A D | papr_hcalls.rst | 28 Hence a Hypercall (hcall) is essentially a request by the pseries guest
36 The ABI specification for a hcall between a pseries guest and PAPR hypervisor
38 done via the instruction **HVCS** that expects the Opcode for hcall is set in *r3*
39 and any in-arguments for the hcall are provided in registers *r4-r12*. If values
44 'HVCS' instruction the return value of the hcall is available in *r3* and any
55 Any hcall should follow same register convention as described in section 2.2.1.1
69 | r3 | Y | hcall opcode/return value |
122 After servicing the hcall, hypervisor sets the return-value in *r3* indicating
123 success or failure of the hcall. In case of a failure an error code indicates
127 In some cases a hcall can potentially take a long time and need to be issued
[all …]
|
| H A D | kvm-nested.rst | 29 KVM: PPC: Book3S HV: Framework and hcall stubs for nested virtualization
38 This API works primarily using a single hcall h_enter_nested(). This
48 it's partition table using the h_set_partition_table() hcall. All
69 hcall.
81 - L1 and L0 communicate the vCPU state using the H_GUEST_{G,S}ET() hcall
83 - L1 requests the L0 runs the vCPU running H_GUEST_VCPU_RUN() hcall
286 hcall.
288 This hcall also has associated input and output GSBs. Unlike
290 parameters to the hcall (This was done in the interest of
299 On exit from the hcall, the output buffer is filled with elements
[all …]
|
| /linux/arch/powerpc/kvm/ |
| H A D | book3s_pr_papr.c | 489 unsigned int hcall; in kvmppc_pr_init_default_hcalls() local
492 hcall = default_hcall_list[i]; in kvmppc_pr_init_default_hcalls()
493 WARN_ON(!kvmppc_hcall_impl_pr(hcall)); in kvmppc_pr_init_default_hcalls()
494 __set_bit(hcall / 4, kvm->arch.enabled_hcalls); in kvmppc_pr_init_default_hcalls()
|
| H A D | book3s_xics.c | 848 int kvmppc_xics_rm_complete(struct kvm_vcpu *vcpu, u32 hcall) in kvmppc_xics_rm_complete() argument
854 hcall, icp->rm_action, icp->rm_dbgstate.raw, icp->rm_dbgtgt); in kvmppc_xics_rm_complete()
|
| /linux/arch/powerpc/platforms/pseries/ |
| H A D | vas.c | 168 int h_query_vas_capabilities(const u64 hcall, u8 query_type, u64 result) in h_query_vas_capabilities() argument
172 rc = plpar_hcall_norets(hcall, query_type, result); in h_query_vas_capabilities()
180 (hcall == H_QUERY_VAS_CAPABILITIES) ? in h_query_vas_capabilities()
|
| /linux/arch/powerpc/include/asm/ |
| H A D | vas.h | 271 int h_query_vas_capabilities(const u64 hcall, u8 query_type, u64 result);
|
| H A D | kvm_ppc.h | 301 int (*hcall_implemented)(unsigned long hcall);
672 extern int kvmppc_xics_rm_complete(struct kvm_vcpu *vcpu, u32 hcall);
701 static inline int kvmppc_xics_rm_complete(struct kvm_vcpu *vcpu, u32 hcall) in kvmppc_xics_rm_complete() argument
|
| /linux/tools/include/uapi/linux/ |
| H A D | kvm.h | 111 } hcall; member
134 } hcall; member
|
| /linux/tools/arch/powerpc/include/uapi/asm/ |
| H A D | kvm.h | 745 __u32 hcall[4]; member
|
| /linux/arch/powerpc/include/uapi/asm/ |
| H A D | kvm.h | 745 __u32 hcall[4]; member
|
| /linux/Documentation/virt/kvm/ |
| H A D | ppc-pv.rst | 207 generic hypercalls are implemented here, like the ePAPR idle hcall. These are
|
| H A D | api.rst | 1854 __u32 hcall[4];
1861 The hcall array defines 4 instructions that make up a hypercall.
1868 /* the host supports the ePAPR idle hcall
2182 When the guest issues an H_PUT_TCE hcall on a liobn for which a TCE
6943 } hcall;
7071 } hcall;
7474 :Parameters: args[0] is the sPAPR hcall number;
7479 handling of an hcall is effective across the VM. On creation, an
7483 not to attempt to handle the hcall, but will always exit to userspace
7488 If the hcall number specified is not one that has an in-kernel
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | kernel-parameters.txt | 5106 Disable RADIX GTSE feature and use hcall for TLB
|