From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 7/8] KVM: Add page map arch callback Date: Tue, 07 Aug 2012 16:58:01 +0300 Message-ID: <50211EE9.4020000@redhat.com> References: <1344337036-22244-1-git-send-email-agraf@suse.de> <1344337036-22244-8-git-send-email-agraf@suse.de> <502118FA.1020007@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "kvm-ppc@vger.kernel.org" , KVM list , "kvmarm@lists.cs.columbia.edu" To: Alexander Graf Return-path: In-Reply-To: Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 08/07/2012 04:44 PM, Alexander Graf wrote: > >> >> Is this the correct place? Who says the caller of hva_to_pfn() is going >> to map it? > > I don't think anyone is. However, we need the struct page, and all the generic kvm mm code tries hard to hide it from its users. The alternative would be to expose all those details, and I'm not sure that's a good idea. > > Essentially, we don't care if we're overly cautious. Clearing one page too much is way better than clearing one too few. Are you sure everyone uses hva_to_pfn()? x86 uses gfn_to_hva_many(), in one place. -- error compiling committee.c: too many arguments to function