From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KQkMc-0002UV-3I for qemu-devel@nongnu.org; Wed, 06 Aug 2008 10:51:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KQkMa-0002QA-8r for qemu-devel@nongnu.org; Wed, 06 Aug 2008 10:51:45 -0400 Received: from [199.232.76.173] (port=35400 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQkMa-0002Px-3x for qemu-devel@nongnu.org; Wed, 06 Aug 2008 10:51:44 -0400 Received: from smtp.eu.citrix.com ([62.200.22.115]:22386) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KQkMZ-0008OO-OH for qemu-devel@nongnu.org; Wed, 06 Aug 2008 10:51:43 -0400 Date: Wed, 6 Aug 2008 15:51:42 +0100 From: Samuel Thibault Subject: Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu Message-ID: <20080806145142.GP4448@implementation.uk.xensource.com> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4899B2CB.8010403@redhat.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: xen-devel@lists.xensource.com, Ian Jackson , qemu-devel@nongnu.org Gerd Hoffmann, le Wed 06 Aug 2008 16:18:51 +0200, a écrit : > Samuel Thibault wrote: > > But by having it merged into just upstream qemu you won't magically get > > Xen people actually test it, so it would be mostly dead code. > > > >> Pretty much like upstreaming the xen support into the linux kernel. > > > > There's a big difference here. The upstream linux kernel merge won't be > > merged back to the linux-2.6.18 tree. > > 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. Samuel