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

[Xen-devel] Re: [PATCH] XML-RPC: Cope with large integers on x86-64 syst

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] XML-RPC: Cope with large integers on x86-64 systems
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Tue, 28 Mar 2006 15:55:10 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 28 Mar 2006 14:56:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <44289F79.9000501@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44289F79.9000501@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Mar 27, 2006 at 08:29:13PM -0600, Anthony Liguori wrote:

> Attached patch fixes a problem in marshaling large integers.  It seems 
> to only occur on systems with very large memory.  However, on those 
> systems, it's a show-stopper.  I see this as a temporary solution until 
> we can sanitize the XML-RPC functions and get rid of all the 
> S-Expression stuff.

Anthony,

This code is clearly plagiarised from Lib/xmlrpclib.py in the Python
distribution, without appropriate credit, copyright and licence statements in
the code, and without a patch to the documentation as per the licence
agreement.  I can't accept this patch as it stands.

Regardless, I don't see what is to be gained in marshalling ints >32bits as
strings, but those <=32 bits as integers; the receiving code is going to have
to convert the incoming argument unconditionally, so why not just send all
integers as strings?  They're going to be stringified on the wire anyway, so
there's no efficiency loss, and I don't think that anyone fancies auditing
Xend to figure out which integers are strict 32 bit integers on all platforms
and which aren't, so it would be safer just to pass them all as strings.

Ewan.

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