diff options
| author | Sheng Yang <sheng@linux.intel.com> | 2010-06-30 12:25:15 +0800 |
|---|---|---|
| committer | Avi Kivity <avi@redhat.com> | 2010-08-01 10:47:21 +0300 |
| commit | f5f48ee15c2ee3e44cf429e34b16c6fa9b900246 (patch) | |
| tree | 75496197219d9aeedd3317fa007cc3b2e414c5da /lib/bcd.c | |
| parent | cf3e3d3e19868ca01da163200bbfc687523df0fc (diff) | |
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>
Diffstat (limited to 'lib/bcd.c')
0 files changed, 0 insertions, 0 deletions