From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KQktr-0001dY-AH for qemu-devel@nongnu.org; Wed, 06 Aug 2008 11:26:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KQktq-0001c9-Kb for qemu-devel@nongnu.org; Wed, 06 Aug 2008 11:26:06 -0400 Received: from [199.232.76.173] (port=52275 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQktq-0001bj-Cs for qemu-devel@nongnu.org; Wed, 06 Aug 2008 11:26:06 -0400 Received: from mx1.redhat.com ([66.187.233.31]:51237) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KQktq-0006KG-9U for qemu-devel@nongnu.org; Wed, 06 Aug 2008 11:26:06 -0400 Message-ID: <4899C281.4040006@redhat.com> Date: Wed, 06 Aug 2008 17:25:53 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu References: <489835A3.6030804@redhat.com> <20080805112935.GO4478@implementation.uk.xensource.com> <48985336.2020709@redhat.com> <20080805150328.GT4478@implementation.uk.xensource.com> <20080805154140.GV4478@implementation.uk.xensource.com> <48997981.1030703@redhat.com> <20080806102338.GA4448@implementation.uk.xensource.com> <4899A617.6040506@redhat.com> <20080806133903.GH4448@implementation.uk.xensource.com> <4899B2CB.8010403@redhat.com> <20080806145142.GP4448@implementation.uk.xensource.com> In-Reply-To: <20080806145142.GP4448@implementation.uk.xensource.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Samuel Thibault , Gerd Hoffmann , Anthony Liguori , qemu-devel@nongnu.org, xen-devel@lists.xensource.com, Ian Jackson 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. cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/