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] Re: [Qemu-devel] [PATCH V9 04/16] xen: Support new libxc

To: Keir Fraser <keir@xxxxxxx>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH V9 04/16] xen: Support new libxc calls from xen unstable.
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Thu, 27 Jan 2011 12:21:03 +0000
Cc: Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, Xen, QEMU-devel <qemu-devel@xxxxxxxxxx>, "Stefano@xxxxxxxxxx" <Stefano@xxxxxxxxxx>, Anthony Liguori <anthony@xxxxxxxxxxxxx>, Anthony Perard <anthony.perard@xxxxxxxxxx>
Delivery-date: Thu, 27 Jan 2011 04:20:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C9671290.1286D%keir@xxxxxxx>
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>
References: <C9671290.1286D%keir@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Thu, 27 Jan 2011, Keir Fraser wrote:
> On 27/01/2011 12:03, "Stefano Stabellini" <stefano.stabellini@xxxxxxxxxxxxx>
> wrote:
> >> Really?  There's no VERSION #define?  Can please fix this upstream so we
> >> don't have to do this forever.
> >  
> > Yeah, it is a bit of a shame but there isn't an #define VERSION in
> > xenctrl.h.
> > If we introduce it now, the first Xen release to have it is going to be
> > 4.1.
> We can add it for 4.1.0 and 4.0.2. Really that covers everyone who'll want
> to build newly upstreamed qemu bits. Gracefully failing to configure in the
> absence of the new define would be quite acceptable imo.

People might want to use qemu just as Xen PV backends provider, as it
works now, so removing Xen support in the absence of the new define
would be a regression in that case.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>