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


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

To: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Markus Armbruster <armbru@xxxxxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxxxxx>, Anthony Liguori <anthony@xxxxxxxxxxxxx>, qemu-devel@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu
From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Date: Wed, 06 Aug 2008 15:54:33 +0200
Delivery-date: Wed, 06 Aug 2008 06:55:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080806125055.GG4448@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: <48973F8E.8080109@xxxxxxxxxxxxx> <20080805104630.GM4478@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <489835A3.6030804@xxxxxxxxxx> <20080805112935.GO4478@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <48985336.2020709@xxxxxxxxxx> <20080805150328.GT4478@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080805154140.GV4478@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <48997981.1030703@xxxxxxxxxx> <20080806102338.GA4448@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <m37iauxqii.fsf@xxxxxxxxxxxxxxxxxxxxx> <20080806125055.GG4448@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080501)

> 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.



Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>