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 20:58:28 +0100 Message-ID: <20101124195828.GA22016@aepfle.de> References: <20101123210158.GA9425@aepfle.de> <20101124102202.GF19638@whitby.uk.xensource.com> <20101124144138.GA25619@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20101124144138.GA25619@aepfle.de> 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, Olaf Hering wrote: > On Wed, Nov 24, Tim Deegan wrote: > > Another option would be to audit all callers of p2m_is_ram() and check > > whether they can handle paged-out PFNs (which I though had already been > > done but seems not to be). Keir's VCPU yield patch might be useful in > > some of those places too. > > I think most if not all is caught by my changes already. A quick grep shows there are a few places that need an audit wether or not the paging types can be removed from p2m_is_ram(). Olaf