On 05/01/2012 12:39 PM, Peter Zijlstra wrote: > On Sun, 2012-04-29 at 15:23 +0300, Avi Kivity wrote: > > On 04/27/2012 07:24 PM, Nikunj A. Dadhania wrote: > > > flush_tlb_others_ipi depends on lot of statics in tlb.c. Replicated > > > the flush_tlb_others_ipi as kvm_flush_tlb_others to further adapt to > > > paravirtualization. > > > > > > Use the vcpu state information inside the kvm_flush_tlb_others to > > > avoid sending ipi to pre-empted vcpus. > > > > > > * Do not send ipi's to offline vcpus and set flush_on_enter flag > > > > get_user_pages_fast() depends on the IPI to hold off page table teardown > > while they are locklessly walked with interrupts disabled. If a vcpu > > were to be preempted while in this critical section, another vcpu > > tearing down page tables would go ahead and destroy them. when the > > preempted vcpu resumes it then touches the freed pages. > > > > We could try to teach kvm and get_user_pages_fast() about this, but this > > is intrusive. Another option is to replace the cpu_relax() loop with > > something that sleeps and is then woken up by the TLB IPI handler if needed. > > I think something like > > select HAVE_RCU_TABLE_FREE if PARAVIRT > > or somesuch is just about all it takes. > > A slightly better option would be to wrap all that tlb_*table* goo into > paravirt stuff and only do the RCU free when paravirt is indeed enabled, > but other than that you're there. I infer from this that there is a cost involved with rcu freeing. Any idea how much? Looks like this increases performance for the overcommitted case, and also for the case where many vcpus are sleeping, while reducing performance for the uncontended, high duty cycle case. > This should work because the preempted vcpu's RCU state would also be > stalled and thus avoids the actual page-table from going away. It can be unstalled at any moment. But spin_lock_irq() > rcu_read_lock(). -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
