kvm/x86/msr.rst

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. This memory is expected to hold the
220 	a token that will be used to notify the guest when missing page becomes
224 	is currently supported, when set, it indicates that the guest is dealing
226 	'flags' is '0' it means that this is regular page fault. Guest is
231 	as regular page fault, guest must reset 'flags' to '0' before it does
238 	Guest is supposed to write '0' to 'token' when it is done handling
256 	same vcpu as 'page not present' event was, but guest should not rely on
264 	in guest RAM, plus an enable bit in bit 0. This memory is expected to
280 	anything with bit0 == 0 is written to it. Guest is required to make sure
286 		a sequence counter. In other words, guest has to check
313 	physical address of a 4 byte memory area which must be in guest RAM and
318 	injection.  Value of 1 means that guest can skip writing EOI to the apic
320 	EOI by clearing the bit in guest memory - this location will
324 	It is always safe for the guest to ignore the optimization and perform
329 	guest does not need to use either lock prefix or memory ordering
334 	guest and clear the least significant bit in the memory area
335 	in the window between guest testing it to detect
336 	whether it can skip EOI apic write and between guest
338 	guest must both read the least significant bit in the memory area and
373 	When the guest is done processing 'page ready' APF event and 'token'
384         CPUID.  Bit 0 represents whether live migration of the guest is allowed.
386         When a guest is started, bit 0 will be 0 if the guest has encrypted
387         memory and 1 if the guest does not have encrypted memory.  If the
388         guest is communicating page encryption status to the host using the
390         allow live migration of the guest.