KVM: VMX: Execute WBINVD to keep data consistency with assigned devices

Browse source

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>

...

This commit is contained in:

Sheng Yang 2010-06-30 12:25:15 +08:00 • committed by Avi Kivity

parent cf3e3d3e19

commit f5f48ee15c

5 changed files with 67 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

arch/x86/include/asm/kvm_host.h

View file

5

arch/x86/kvm/emulate.c

View file

7

arch/x86/kvm/svm.c

View file

10

arch/x86/kvm/vmx.c

View file

41

arch/x86/kvm/x86.c

View file