Lines Matching full:guest

25 	in guest RAM. This memory is expected to hold a copy of the following
40 		guest has to check version before and after grabbing
64 	guest RAM, plus an enable bit in bit 0. This memory is expected to hold
87 		guest has to check version before and after grabbing
127 		coordinated between the guest and the hypervisor. Availability
139 		|	    |		   | guest vcpu has been paused by    |
196 	which must be in guest RAM and must be zeroed. This memory is expected
221 	a token that will be used to notify the guest when missing page becomes
225 	is currently supported, when set, it indicates that the guest is dealing
227 	'flags' is '0' it means that this is regular page fault. Guest is
232 	as regular page fault, guest must reset 'flags' to '0' before it does
238 	present' event. The event indicates the page in now available. Guest is
257 	same vcpu as 'page not present' event was, but guest should not rely on
265 	in guest RAM, plus an enable bit in bit 0. This memory is expected to
281 	anything with bit0 == 0 is written to it. Guest is required to make sure
287 		a sequence counter. In other words, guest has to check
314 	physical address of a 4 byte memory area which must be in guest RAM and
319 	injection.  Value of 1 means that guest can skip writing EOI to the apic
321 	EOI by clearing the bit in guest memory - this location will
325 	It is always safe for the guest to ignore the optimization and perform
330 	guest does not need to use either lock prefix or memory ordering
335 	guest and clear the least significant bit in the memory area
336 	in the window between guest testing it to detect
337 	whether it can skip EOI apic write and between guest
339 	guest must both read the least significant bit in the memory area and
374 	When the guest is done processing 'page ready' APF event and 'token'
385         CPUID.  Bit 0 represents whether live migration of the guest is allowed.
387         When a guest is started, bit 0 will be 0 if the guest has encrypted
388         memory and 1 if the guest does not have encrypted memory.  If the
389         guest is communicating page encryption status to the host using the
391         allow live migration of the guest.