From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH 00/18] xenpaging changes for 4.0 Date: Mon, 18 Oct 2010 15:06:45 +0200 Message-ID: <20101018130645.GB22126@aepfle.de> References: <20101015141202.309585877@aepfle.de> <20101018112601.GP4007@whitby.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20101018112601.GP4007@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: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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. Thats currently beyond my knowledge, sorry. Any pointer for how to do that are welcome. > - The usual way to get patches into the 4.0 tree is to submit them > againts xen-unstable and then ask for specific patches to be > backported; I see you're already going that way with most of these. Yes, just wanted to send my current state and all of them are also needed for xen-unstable > - I imagine the tools maintainers will encourage you to do your tools > patches againsl xl/libxl as well. :) Sure, that will be done as well. Olaf