From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takuya Yoshikawa Subject: Re: [PATCH v2 3/5] KVM: Flush TLB in mmu notifier without holding mmu_lock Date: Mon, 2 Jul 2012 23:09:41 +0900 Message-ID: <20120702230941.543cdf9eb7f6630cf8503b19@gmail.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> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , Xiao Guangrong , Takuya Yoshikawa , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mail-yw0-f51.google.com ([209.85.213.51]:60023 "EHLO mail-yw0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752687Ab2GBOJr (ORCPT ); Mon, 2 Jul 2012 10:09:47 -0400 Received: by yhnn12 with SMTP id n12so5842322yhn.10 for ; Mon, 02 Jul 2012 07:09:46 -0700 (PDT) In-Reply-To: <4FF196FA.9020309@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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. Thanks, Takuya