From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tim Deegan <Tim.Deegan@citrix.com>
Subject: [PATCH 0 of 4] RFC: Nested-p2m cleanups and locking
	changes
Date: Wed, 22 Jun 2011 17:10:26 +0100
Message-ID: <patchbomb.1308759026@whitby.uk.xensource.com>
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
Cc: Christoph Egger <Christoph.Egger@amd.com>
List-Id: xen-devel@lists.xenproject.org


This patch series tidies up a few bits ofthe nested p2m code. 
The main thing it does is reorganize the locking so that most of the 
changes to nested p2m tables happen only under the p2m lock, and the 
nestedp2m lock is only needed to reassign p2m tables to new cr3 values.

Unfortunately I'm having terrible trouble trying to run Xen under Xen 
to test these, so this version of the series is only compile-tested.
I'm just posting them for feedback from Christoph on whether this approach
seems reasonable. 

Cheers,

Tim.