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

Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid

To: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 1 Jul 2008 18:38:25 +0100
Cc: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>, Kevin Wolf <kwolf@xxxxxxx>
Delivery-date: Tue, 01 Jul 2008 10:39:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080626163844.GW20952@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/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: <486322FE.3070304@xxxxxxxxxxxxx> <48637B96.9090606@xxxxxxx> <18531.43971.119239.17511@xxxxxxxxxxxxxxxxxxxxxxxx> <20080626163844.GW20952@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Daniel P. Berrange writes ("Re: [Xen-devel] [PATCH] Log qemu-dm's message with 
date, time and pid"):
> What are your plans wrt to QEMU longer term ?  Are you going to merge this
> GIT repo into tools/ioemu in xen-unstable.hg, or thinking its better to
> keep a separate tree on an ongoing basis ?

No, I don't think it's practical to keep this tree in
xen-unstable.hg.  Everyone else doing work on qemu is using git (or
svn).

>  Would we have synced up 
> releases of the two, or try to apply some ABI stability to libxc and 
> libxenstore APIs to allow separate release of QEMU vs XenD tools ?

Releases of ioemu will follow releases of Xen, but commits will be
made separately.  So there will be at least some compatibility
arrangements.  I'm generally a fan of putting backward compatibility
in interfaces, but I think for now we won't be making any promises.

>  The latter could be interesting because apps like Xenner are able
> to use QEMU-DM in isolation from the rest of the XenD stack.

I certainly don't see any reason to go out of my way to prevent that :-).

Ian.

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