Lines Matching full:l0

12 hypervisor has implemented them. The terms L0, L1, and L2 are used to
13 refer to different software entities. L0 is the hypervisor mode entity
15 guest virtual machine that is directly run under L0 and is initiated
16 and controlled by L0. L2 is a guest virtual machine that is initiated
22 Linux/KVM has had support for Nesting as an L0 or L1 since 2018
24 The L0 code was added::
39 call made by the L1 to tell the L0 to start an L2 vCPU with the given
40 state. The L0 then starts this L2 and runs until an L2 exit condition
42 the L1 by the L0. The full L2 vCPU state is always transferred from
43 and to L1 when the L2 is run. The L0 doesn't keep any state on the L2
44 vCPU (except in the short sequence in the L0 on L1 -> L2 entry and L2
47 The only state kept by the L0 is the partition table. The L1 registers
49 other state held by the L0 about the L2s is cached state (such as
52 The L1 may run any L2 or vCPU without first informing the L0. It
74 - L1 and L0 negotiate capabilities with H_GUEST_{G,S}ET_CAPABILITIES()
77 - L1 requests the L0 create an L2 with H_GUEST_CREATE() and receives a token
79 - L1 requests the L0 create an L2 vCPU with H_GUEST_CREATE_VCPU()
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
94 an L1 or L0. Latest version of PAPR can be referred to for more details.
96 All these HCALLs are made by the L1 to the L0.
101 This is called to get the capabilities of the L0 nested
117 This is called to inform the L0 of the capabilities of the L1
122 subset of the flags returned from GET. This process allows the L0 and
198 The L1 writes only the IDs and sizes in the GSB.  L0 writes the
212            over ownership of the VCPU state and that the L0 can free
249 The L1 writes all values in the GSB and the L0 only reads the GSB for
300 determined by the L0. The reason for the exit is contained in GPR4 (ie
308 the L1 may set a flag (as a hcall parameter) and the L0 will
350 L0 in the case of kdump/kexec::
367 about the L2 between the L1 and L0 via H_GUEST_{G,S}ET() and
415 | 0x0001 | 0x08  | R  |   G    | Size of L0 vCPU state. See:      |
603 h_enter_nested() call and the L0 ensures they end up as the L2 state
611 In the v1 API, all state is sent from the L1 to the L0 and vice versa
612 on every h_enter_nested() hcall. If the L0 is not currently running
613 any L2s, the L0 has no state information about them. The only
617 The v2 API changes this so that the L0 retains the L2 state even when
619 communicate with the L0 about L2 state when it needs to modify the L2
630 to the L0 until that L2 vcpu runs again. Hence when the L1 updates
632 copy and only flushes this copy to the L0 when the L2 runs again via