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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] tmem (tools-side): ABI v1 to handle long object-

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] tmem (tools-side): ABI v1 to handle long object-ids (XEN-UNSTABLE)
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Fri, 3 Sep 2010 18:50:24 +0100
Cc: "Xen-Devel \(xen-devel@xxxxxxxxxxxxxxxxxxx\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Fri, 03 Sep 2010 10:51:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <b9b13d56-0bbc-4ea2-b8e8-ab1dbcdd521c@default>
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>
Newsgroups: chiark.mail.xen.devel
References: <b9b13d56-0bbc-4ea2-b8e8-ab1dbcdd521c@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Dan Magenheimer writes ("[Xen-devel] [PATCH] tmem (tools-side): ABI v1 to 
handle long object-ids (XEN-UNSTABLE)"):
> tmem (tools-side): move to new ABI version to handle
> long object-ids

Thanks for this patch.

I'm sad to say that this appears to confirm that the decision by the
world in general not to use tmem yet was correct.  After all if they
_were_ using it now they'd have some pain.

I don't have a strong opinion about this patch.  The tools part seems
reasonably well-contained so I guess I'm happy to see it applied.

> Please apply to XEN-UNSTABLE ... see separate post for
> the essentially identical xen-4.0-testing equivalent.

It would probably be best if Keir applied both patches in a single
changeset, to avoid build breakage.

It would be easier to find your messages if your patchbomb script (or
your mailer, if you're doing it by hand) could be persuaded to post
all the portions of a series in a single thread, with appropriate
In-Reply-To and References headers.


Xen-devel mailing list