From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: bogus gfn - mfn - gfn - mfn checks in guest_physmap_add_entry Date: Wed, 24 Nov 2010 16:00:18 +0100 Message-ID: <20101124150018.GA10411@aepfle.de> References: <20101123210158.GA9425@aepfle.de> <20101124102202.GF19638@whitby.uk.xensource.com> <20101124144138.GA25619@aepfle.de> <20101124145326.GH19638@whitby.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20101124145326.GH19638@whitby.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tim Deegan Cc: Patrick Colp , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Wed, Nov 24, Tim Deegan wrote: > The guest_physmap_add_entry code, and the p2m audit code, would be made > more reliable if, say, alloc_domheap_pages and/or free_domheap_pages > zapped the m2p entries for MFNs they touched. Ok, if thats the ultimate place where mfns come and go, I will make my changes there. Olaf