From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: [PATCH 00/12] xenpaging changes for xen-unstable
Date: Mon, 10 Jan 2011 17:43:45 +0100
Message-ID: <20110110164345.521919826@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.

New to this series since my last post are patch 1 to 5.
They are likely non-controversial and could be applied.

Patches 6 and 7 are required to maintain the machine_to_phys_mapping[]
array properly. Unless there are objections to the deallocation part,
they could be applied.

Patch 8 could be applied as well.

All other changes are not ready yet for inclusion.

As it stands right now, a guest will hang hard with xenpaging once the
balloon driver is loaded in the guest. Its not clear what the issue is,
no memory_op hypercall has been issued yet. xm vcpu-list indicates the
guest makes no progress.  I will debug this further.


Olaf