WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 0 of 5] p2m synchronization groundwork

To: Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0 of 5] p2m synchronization groundwork
From: Tim Deegan <tim@xxxxxxx>
Date: Thu, 10 Nov 2011 12:27:13 +0000
Cc: olaf@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, George.Dunlap@xxxxxxxxxxxxx, andres@xxxxxxxxxxxxxx, keir.xen@xxxxxxxxx, adin@xxxxxxxxxxxxxx
Delivery-date: Thu, 10 Nov 2011 04:27:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <patchbomb.1320722908@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <patchbomb.1320722908@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
At 22:28 -0500 on 07 Nov (1320704908), Andres Lagar-Cavilla wrote:
> This patch series lays the groundwork for improving the synchronization
> of primitives accessing the p2m.
> 
> This is a partial repost of the patches emailed previously as a RFC. 
> These patches are now intended for committing to the tree.
> 
> We change the API for accessing the p2m to a family of functions
> get_gfn/put_gfn. The name intends to reflect the fact that even lookups
> are meant to obtain exclusive access to a p2m entry, and that said access
> should be relinquished (put_gfn) when done.
> 
> The patches, however, alter little functionality. The API name change 
> does not involve yet additional locking or ref-counting. They will, however,
> throw a "barrier" that will force any new commits to conform to the new API.
> 
> Patches are based off 24066:54a5e994a241. Should the new XENMEM calls be 
> accepted before this, the series needs to be updated to also change the API
> there.
> 
> Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.

Patches 0-4 applied, thanks.  I've reviewed patch 5 separately. 

Cheers,

Tim.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel