From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: [PATCH 00/21] xenpaging changes for xen-unstable
Date: Fri, 26 Nov 2010 14:49:01 +0100
Message-ID: <20101126134901.384130351@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.

Patches 1 to 14 are likely non-controversial and could be applied.
All later patches need more review (15/16), and more work from my side (17+).

With a similar series of changes for 4.0.1 my testcase, which is a continuous
reboot of a Linux guest, passes now. It ran for more than 1000 iterations and
exercised the early bootcode.

There are still some issues like guests not starting up when running the
reboot loop with 4x1G guests parallel on a 4GB box with all guest memory paged.
This seems to happen when the guest initially needs the full 1G until
xenpaging frees that memory again.

Other than that, xenpaging is now more mature.
I havent seen data corruption anymore.

Olaf