From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: [PATCH 00/16] xenpaging changes for xen-unstable
Date: Tue, 02 Nov 2010 23:30:10 +0100
Message-ID: <20101102223010.603002116@aepfle.de>
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org


Here are some changes for xenpaging in xen-unstable.

Its just for review and comments.

In a previous series for 4.0 I had a retry loop for the XENMEM_* commands.
This could be done in a different way to prevent changes to existing kernel
drivers in the guest. The changes to guest_physmap_add_entry are not needed
with the update for machine_to_phys_mapping handling.
But the patch to handle guest_remove_page does not work as expected, the guest
will hang. Any help to get this fixed without retry loops is appreciated.

Olaf