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] [PATCH 00/10] xen: pv domain support.

To: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 00/10] xen: pv domain support.
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Tue, 21 Apr 2009 16:25:46 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, qemu-devel@xxxxxxxxxx
Delivery-date: Tue, 21 Apr 2009 08:26:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1240316408-15949-1-git-send-email-kraxel@xxxxxxxxxx>
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>
Newsgroups: chiark.mail.xen.devel
References: <1240316408-15949-1-git-send-email-kraxel@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Gerd Hoffmann writes ("[Xen-devel] [PATCH 00/10] xen: pv domain support."):
> Next round, addressing review comments:
> Ian, is just pulling from git fine with you?  Or do you want the
> qemu-xen patches mailed to xen-devel?

I think that for form's sake it would be good for you to mail the
patches to xen-devel but I'm happy to pull.  So ideally a patch series
submission which says `here are the diffs 0/n and also a git URL'.
Is that a lot of work for you ?  If so I can probably produce such a
series of emails myself but I think since you're the originator of
these patches I think it would make more sense for you to do it.

Thanks for your contributions.  I'm definitely keen to have them and
I'll be branching qemu-xen so that I can take your changes now rather
than waiting for the Xen 3.4 release freeze to end.

It's good that you're posting this code to qemu-devel and getting
review there.  But I'd like the qemu developers to hold off committing
these changes to their tree until the files which are being added are
100% identical in Gerd's patch series to in qemu-xen-unstable.

That way qemu upstream will remain directly mergeable into
qemu-xen-unstable because the code in the new files will be identical.
Anything else will make my life very painful.

To make this happen I'm of course happy to take patches to make sure
that the code which is in qemu-xen-unstable is in the form that qemu
upstream want it for merging.


Xen-devel mailing list