This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH 00/18] xenpaging changes for 4.0

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 00/18] xenpaging changes for 4.0
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Mon, 18 Oct 2010 15:06:45 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 18 Oct 2010 06:07:24 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1287407208; l=957; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=k6gc0GkQvQ5N6IbYYjcd1GQqLuE=; b=Fup61GZKgI/YmuPI97iqgpfIX9XDsrSpzPgbM3xrF04yGzvfLl9KfxIAzrnJbZzxE5h pN4q4BR5S1TF/ZyEMniGQLZ8GT3vamcmaKUmMmjE/7j0UrNlp73cOjfAE0SN+DVvyzBXW B2f3GgmSJfDRp7Kyiux4bCWR06MRU7c77nQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101018112601.GP4007@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20101015141202.309585877@xxxxxxxxx> <20101018112601.GP4007@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
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.


Xen-devel mailing list