Lines Matching refs:hcall

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
131 servicing the hcall yet.
135 for each subsequent hcall until hypervisor returns a non *H_CONTINUE*
286 The hcall returns H_BUSY when the flush takes longer time and the hcall needs
289 subsequent hcalls to the hypervisor until the hcall is completely serviced