[Xen-devel] New memparse function collides with Xen/ia64

To:	<xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] New memparse function collides with Xen/ia64
From:	"Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date:	Thu, 19 May 2005 12:46:30 -0700
Delivery-date:	Thu, 19 May 2005 19:46:26 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcVcq3PwXEQOOecqSEaNE6Uoi8ckMg==
Thread-topic:	New memparse function collides with Xen/ia64

It appears there is a new function API between
common and archdep called memparse().  Unfortunately,
Xen/ia64 already implements that in archdep code,
using the standard Linux code and function interface
(which hasn't changed since at least 2.4.7), and
the new xen/common/lib.c code uses virtually the
same code but a new slightly different API.

Could you either:
1) move the new definition to x86-archdep code, or
2) change the API to the Linux one, remove it from
   xen/common/lib.c and add a brand new common/cmdline.c
   (which can be cloned from linux/lib/cmdline.c), or
3) change the API to put the second return-through-pointer
   parameter back (and leave it in xen/common/lib.c)

I prefer (2).

Thanks,
Dan

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] New memparse function collides with Xen/ia64