From mboxrd@z Thu Jan  1 00:00:00 1970
From: Brendan Cully <brendan@cs.ubc.ca>
Subject: [PATCH 0 of 2] Remus updates
Date: Wed, 02 Dec 2009 21:22:20 -0800
Message-ID: <patchbomb.1259817740@zanzibar>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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

The memory pool patch broke Remus' (hacky) call to balloon.free to
allocate log-dirty memory. The first patch fixes this by being a
little less intimate with xend internals.

The second patch allows Remus to checkpoint PV guests that lack a
suspend event channel. This is primarily targetted at
pvops. Unfortunately, pvops currently has a bug handling
suspend-cancel, but when that is fixed Remus should support it.