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, RFC 1/4] linux: add new (replacement) mmap-batch

To: Jan Beulich <JBeulich@xxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH, RFC 1/4] linux: add new (replacement) mmap-batch ioctl
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 12 Jan 2010 07:57:25 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 11 Jan 2010 23:58:27 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B4C36B00200007800029431@xxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqTWz+DjzMDvp0TTjuopVWiCgwMWQAAaE0v
Thread-topic: [Xen-devel] [PATCH, RFC 1/4] linux: add new (replacement) mmap-batch ioctl
User-agent: Microsoft-Entourage/12.23.0.091001
On 12/01/2010 07:45, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>> As does MMAPBATCH2. I actually strongly suggest IOCTL_PRIVCMD_MMAPBATCH_V2,
>> which makes the situation even more crystal clear. Distinguishing based on a
>> single underscore, to make the new name 'nice', is misplaced aestheticism.
>> In particular, the tools end up referencing both names (for compatibility)
>> and a clearer name makes the code more intelligible.
> 
> Okay, I'll change the name then. Before re-spinning the set, are there
> any other items that need fixing? Comments on the questions raised?

Looked okay to me. The only question I saw was regarding
xc_get_pfn_type_xxx: I don't think they are used outside libxc, so you can
do whatever makes internal sense for libxc (and remove the decls from
xenctrl.h).

> And are there chances this will still make 4.0? If not, can we at least
> add the interface definitions as place holders (similar to e.g. tmem
> before 3.4), allowing consuming code to be prepared for the addition?

It could go in for 4.0.0-rc2 I suppose.

 -- Keir



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