From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v2 3/5] KVM: Flush TLB in mmu notifier without holding mmu_lock Date: Mon, 02 Jul 2012 17:18:52 +0300 Message-ID: <4FF1ADCC.5060102@redhat.com> References: <1337250284-18607-1-git-send-email-avi@redhat.com> <1337250284-18607-3-git-send-email-avi@redhat.com> <20120521205850.GA27076@amt.cnet> <4FF18E7D.7020102@redhat.com> <4FF196FA.9020309@redhat.com> <20120702230941.543cdf9eb7f6630cf8503b19@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , Xiao Guangrong , Takuya Yoshikawa , kvm@vger.kernel.org To: Takuya Yoshikawa Return-path: Received: from mx1.redhat.com ([209.132.183.28]:59976 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751173Ab2GBOTB (ORCPT ); Mon, 2 Jul 2012 10:19:01 -0400 In-Reply-To: <20120702230941.543cdf9eb7f6630cf8503b19@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/02/2012 05:09 PM, Takuya Yoshikawa wrote: > On Mon, 02 Jul 2012 15:41:30 +0300 > Avi Kivity wrote: > >> kvm_mmu_slot_remove_write_access: same. It's hard to continue the loop >> after a lockbreak though. We can switch it to be rmap based instead. > > Switching to rmap based protection was on my queue before, but I wanted > to do that after your work. It makes sense. I'll dive back in after we agree on the way to go. -- error compiling committee.c: too many arguments to function