From: Tim Deegan Subject: Re: [PATCH 00/18] xenpaging changes for 4.0 Date: Fri, 22 Oct 2010 10:04:45 +0100 Message-ID: <20101022090445.GS4007@whitby.uk.xensource.com> References: <20101015141202.309585877@aepfle.de> <20101018112601.GP4007@whitby.uk.xensource.com> <20101018130645.GB22126@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Return-path: Content-Disposition: inline In-Reply-To: <20101018130645.GB22126@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: Olaf Hering Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org At 14:06 +0100 on 18 Oct (1287410805), Olaf Hering wrote: > On Mon, Oct 18, Tim Deegan wrote: > > > These patches look pretty good to me, with a few caveats: > > - Is it possible to avoid having quite so many paths return ENOENT? > > In particular, there seemed to be paths where _removing_ a p2m entry > > that's paged out caused an error. Would it be possible to have some of > > those cases fixed up from the paging code instead? > > I'm not sure if thats possible. OK, having had a look I'm not sure it's possible either. :) Your current approach should be OK. Cheers, Tim. -- Tim Deegan Principal Software Engineer, XenServer Engineering Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)