From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KQjTQ-00049n-Dg for qemu-devel@nongnu.org; Wed, 06 Aug 2008 09:54:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KQjTP-00049X-19 for qemu-devel@nongnu.org; Wed, 06 Aug 2008 09:54:44 -0400 Received: from [199.232.76.173] (port=54497 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQjTO-00049U-RQ for qemu-devel@nongnu.org; Wed, 06 Aug 2008 09:54:42 -0400 Received: from mx1.redhat.com ([66.187.233.31]:55235) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KQjTO-000740-Gq for qemu-devel@nongnu.org; Wed, 06 Aug 2008 09:54:42 -0400 Message-ID: <4899AD19.8060606@redhat.com> Date: Wed, 06 Aug 2008 15:54:33 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu References: <48973F8E.8080109@codemonkey.ws> <20080805104630.GM4478@implementation.uk.xensource.com> <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> <20080806125055.GG4448@implementation.uk.xensource.com> In-Reply-To: <20080806125055.GG4448@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 , Markus Armbruster , Gerd Hoffmann , Anthony Liguori , qemu-devel@nongnu.org, xen-devel@lists.xensource.com, Ian Jackson Hi, > Baby steps are much easier to review. That's how things are usually > done, and here it looks to me like it is feasible to achieve in Xen (and > have it tested) before event thinking about importing a pile of code in > qemu where it won't receive as much testing as the xen-unstable tree > receives. IMHO the best way to address this issue is to rebase frequently. The xen-unstable testing will also covers qemu then. It also keeps the delta smaller and makes it easier to test qemu patches in qemu-dm. I'm trying to fiddle my bits into qemu-dm right now. One problem is that I get build failures simply because of the fact that the qemu-dm base is old compared to upstream qemu. It would also be great if you can clean up the header mess. qemu-dm doesn't build without xen-unstable.hg. And just a checked out tree isn't good enougth, it must be compiled because qemu-dm depends on some generated header files. Aiee. IMHO qemu-dm should only need /usr/include/xen. If headers are missing there, they should be installed. cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/