From mboxrd@z Thu Jan  1 00:00:00 1970
From: Linda <lindaj@jma3.com>
Subject: coding standards
Date: Mon, 30 Mar 2015 12:29:41 -0600
Message-ID: <55199615.1020000@jma3.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>, Julien Grall <julien.grall@citrix.com>, Lars Kurth <lars.kurth.xen@gmail.com>
List-Id: xen-devel@lists.xenproject.org

Hi Wei,
     I have a few questions before we chat Tuesday.  Per your 
instructions, I read the coding standards, which referred me to libxl.h 
for memory management.  They are contradictory, in that the coding 
standards imply that I should be using internal libxl_*alloc functions, 
but the memory management section says to do a malloc. I thought someone 
should know.
     I assume I should look for and use the appropriate libxl_*alloc 
function.
     Also, you mentioned that all libxl functions should take a ctx 
(context?) as the first argument.  I had looked at several libxl_bitmap* 
functions (init, test, set, and dispose) which don't, but looking at the 
alloc code you sent me, I'm not clear on the purpose of the ctx.  
Perhaps we can go over that in our chat.

Thanks.

Linda