Lines Matching full:guest

25  * reflected to the PR guest kernel, so registers may be set up for
28  * and CR0, so PR-KVM can not support a guest kernel that preserves
53  * guest R9-R13, CTR, CFAR, PPR saved in PACA EX_xxx save area
54  * guest (H)DAR, (H)DSISR are also in the save area for relevant interrupts
55  * guest R13 also saved in SCRATCH0
59  * R9		= guest CR
105 	 * R12		= (guest CR << 32) | interrupt vector
107 	 * guest R12 saved in shadow HSTATE_SCRATCH0
108 	 * guest R13 saved in SPRN_SCRATCH0
127  * the faulting instruction in guest memory from the hypervisor without
130  * When the guest takes a fault that requires the hypervisor to load the
132  * and the guest MMU context loaded. It sets KVM_GUEST_MODE_SKIP, and sets
134  * but loads and stores will access the guest context. This is used to load
135  * the faulting instruction using the faulting guest effective address.
137  * However the guest context may not be able to translate, or it may cause a
145  * read guest memory.
186  * Enter the guest on a ISAv3.0 or later system.
267  * above if the interrupt was taken for a guest that was entered via
270  * The exit code recovers the host stack and vcpu pointer, saves all guest GPRs
271  * and CR, LR, XER as well as guest MSR and NIA into the VCPU, then re-
273  * kvmppc_p9_enter_guest() function, which saves CTR and other guest registers
336 	 * way out of the guest.
338 	 * The link stack won't match coming out of the guest anyway so the
350  * Took an interrupt somewhere right before HRFID to guest, so registers are
367 	 * Clean up guest registers to give host a chance to run.
412 	 * guest r1 if it looks like a kernel stack, so just load the