From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 5/8] KVM: Add hva_to_memslot Date: Sun, 12 Aug 2012 14:21:33 +0300 Message-ID: <502791BD.2070600@redhat.com> References: <1344337036-22244-1-git-send-email-agraf@suse.de> <1344337036-22244-6-git-send-email-agraf@suse.de> <20120809193441.f8336b66.yoshikawa.takuya@oss.ntt.co.jp> <502392A6.7070404@redhat.com> <50277659.3080107@redhat.com> <623895C2-40C1-48C8-B3DF-DA1FFFE742B4@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Takuya Yoshikawa , "kvm-ppc@vger.kernel.org" , KVM list , "kvmarm@lists.cs.columbia.edu" To: Alexander Graf Return-path: In-Reply-To: <623895C2-40C1-48C8-B3DF-DA1FFFE742B4@suse.de> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 08/12/2012 02:03 PM, Alexander Graf wrote: > > Well, for now I just dropped the whole thing. In general, chances are pretty good that an HVA we get notified on with mmu notifiers is representing guest memory. And flushing a few times too often shouldn't hurt. That is not the case, actually. We did this optimization for x86 for this reason. -- error compiling committee.c: too many arguments to function