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


[Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu

To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxxxxx>, Anthony Liguori <anthony@xxxxxxxxxxxxx>, qemu-devel@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Wed, 06 Aug 2008 17:25:53 +0200
Delivery-date: Wed, 06 Aug 2008 08:26:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080806145142.GP4448@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <489835A3.6030804@xxxxxxxxxx> <20080805112935.GO4478@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <48985336.2020709@xxxxxxxxxx> <20080805150328.GT4478@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080805154140.GV4478@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <48997981.1030703@xxxxxxxxxx> <20080806102338.GA4448@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4899A617.6040506@xxxxxxxxxx> <20080806133903.GH4448@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4899B2CB.8010403@xxxxxxxxxx> <20080806145142.GP4448@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080501)
Samuel Thibault wrote:
>> Oh, we can also arrange things without merging back.  Stop rebasing
>> qemu-dm (pretty much like 2.6.18), additionally hook upstream qemu as-is
>> into testing (like pv_ops kernels).  Then start submitting patches to
>> qemu.  When done, zap old qemu-dm.
> Again, there's a difference.  The interface between Linux and Xen has
> always been meant to be a "public" thing.  The interface between ioemu
> and the other xen components has not, and changing it is considered fine
> (we still do it).  Sure that could be cleaned up, but that's probably
> not something that should happen on the upstream qemu side.

Hmm.  That makes me think that starting over from scratch really is the
best option.  Drop the old cruft, design a clean interface, code it up,
discuss it in public and submit to upstream qemu.



Xen-devel mailing list