Gregory Haskins wrote: > On Tue, 2007-07-31 at 17:18 +0800, Dong, Eddie wrote: > >> >> I may miss something, why does that matter? > > As it turns out, it doesn't ;) So we have dropped the patch. But not > for the reason you are suggesting. > > >> __vcpu_clear will eventually >> get executed though it is a little bit delayed. vmclear will >> eventually dump internal state of VM-a VMCS to memory and VM-b get >> its own VMCS loaded. Here the point is vmclear has a parameter to >> identify which VM's VMCS to dump, not only a memory address. Jun, >> please correct me if I am wrong. > > The race is against per_cpu(current_vmcs), not the actual VMCS. > However, Avi pointed out that the race is benign so the race doesn't > matter. > > > -Greg
I see, thanks very much! Eddie ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
