Sheng Yang f5f48ee15c KVM: VMX: Execute WBINVD to keep data consistency with assigned devices ... Some guest device driver may leverage the "Non-Snoop" I/O, and explicitly WBINVD or CLFLUSH to a RAM space. Since migration may occur before WBINVD or CLFLUSH, we need to maintain data consistency either by: 1: flushing cache (wbinvd) when the guest is scheduled out if there is no wbinvd exit, or 2: execute wbinvd on all dirty physical CPUs when guest wbinvd exits. Signed-off-by: Yaozu (Eddie) Dong <eddie.dong@intel.com> Signed-off-by: Sheng Yang <sheng@linux.intel.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>		2010-08-01 10:47:21 +03:00
..
asm	KVM: VMX: Execute WBINVD to keep data consistency with assigned devices	2010-08-01 10:47:21 +03:00