From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andres Lagar-Cavilla" Subject: Re: [PATCH 1 of 3] Use memops for mem paging, sharing, and access, instead of domctls Date: Thu, 9 Feb 2012 12:33:53 -0800 Message-ID: <068d8391fbb2862699b6a8c481ceb7ec.squirrel@webmail.lagarcavilla.org> References: <20276.177.301401.848136@mariner.uk.xensource.com> Reply-To: andres@lagarcavilla.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20276.177.301401.848136@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: andres@gridcentric.ca, xen-devel@lists.xensource.com, tim@xen.org, adin@gridcentric.ca List-Id: xen-devel@lists.xenproject.org > Andres Lagar-Cavilla writes ("[Xen-devel] [PATCH 1 of 3] Use memops for > mem paging, sharing, and access, instead of domctls"): >> We retain the domctl interface for setting up and tearing down >> paging/sharing/mem access for a domain. But we migrate all the per page >> operations to use the memory_op hypercalls (e.g XENMEM_*). > > The tools part of this looks sensible (and pretty formulaic) to me. > > Acked-by: Ian Jackson > > It'll need a hypervisor maintainer to approve the innards. Both this and the next patch have been acked by Tim Deegan on the hypervisor side. However, I have not tested these in isolation. I've always used them preceded by the "locking p2m series" posted earlier. I would suggest that you hold off applying this until the locking p2m series gets applied. I don't think there should be any problems, but I'm being conservative here. Thanks! Andres > > Ian. >