From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: future plans for libxl? Date: Thu, 15 Apr 2010 15:24:23 +0100 Message-ID: <4BC72197.5060601@eu.citrix.com> References: <4BC578DF.9000508@amd.com> <4BC6BE62.3020000@amd.com> <4BC6C374.7030907@eu.citrix.com> <4BC6CCD8.9080509@amd.com> <19399.6727.488013.657578@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19399.6727.488013.657578@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: Andre Przywara , "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 15/04/10 14:53, Ian Jackson wrote: > Perhaps rather than expecting the libxl caller to include > xen/include/public/version.h, it would be better to have a single > libxc call that fills in a single structure by making all the relevant > calls and copying the data out. > > Vincent, Stefano, what do you think ? > That's fine if it happens, but it's not like it's performance critical or will ever be. not adding a new version hypercall and doing it in a series of hypercalls, means that the code stays compatible with old hypervisor. -- Vincent