Re: [PATCH v5] KVM: VMX: Execute WBINVD to keep data consistency with assigned devices

Avi Kivity
2010-06-29T09:39:43Z

On 06/29/2010 06:16 AM, Sheng Yang wrote:
> 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.
>
>

Looks good.

--
error compiling committee.c: too many arguments to function