From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KY4kA-0000c5-2u for qemu-devel@nongnu.org; Tue, 26 Aug 2008 16:02:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KY4k8-0000an-Ta for qemu-devel@nongnu.org; Tue, 26 Aug 2008 16:02:21 -0400 Received: from [199.232.76.173] (port=46470 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KY4k8-0000aX-L9 for qemu-devel@nongnu.org; Tue, 26 Aug 2008 16:02:20 -0400 Received: from mx2.redhat.com ([66.187.237.31]:56698) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KY4k7-0001Fk-DD for qemu-devel@nongnu.org; Tue, 26 Aug 2008 16:02:20 -0400 Message-ID: <48B460D5.9060606@redhat.com> Date: Tue, 26 Aug 2008 22:00:21 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 13/13] xen: pv domain builder. References: <1219336054-15919-1-git-send-email-kraxel@redhat.com> <18611.56835.635884.646447@mariner.uk.xensource.com> <48B3FD5A.4040005@redhat.com> <18612.439.24867.23222@mariner.uk.xensource.com> <48B40AE8.3070008@redhat.com> <18612.4315.494845.442801@mariner.uk.xensource.com> In-Reply-To: <18612.4315.494845.442801@mariner.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: Ian Jackson Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org >> Patches 02 -> 04 pull depending patches, once you've merged with >> upstream they are not needed any more and will be removed from the patch >> set. >> >> Patches 05 -> 09 is the backend core / console / framebuffer stuff you >> are willing to take. >> >> Patch 10 are the xen_machine_pv.c changes (upstream changeset has this >> earlier, moved here for better bisectability). >> >> Patch 11+ are disk + nic backends. Ignore them if you don't want them. > I'll take a more thorough look at 02-06. Do they in your opinion make > sense on their own in qemu-xen-unstable ? 02 -> 04 Make sense if you want to *test* the patches without merging with upstream qemu before. For *merging* the patches I'd suggest to merge from upstream qemu instead, then wait for me rebasing the patchset (and dropping these patches). 05 -> 06 backend core. 07 switches the console to the new backend core. 08 xenfb.c -> xen_framebuffer.c rename. 09 switch framebuffer to new backend core. 05 + 06 alone are not useful as nobody uses the new backend core then. Merging 07 too gives at least one user. 08+09 going in gives a second user. They are a nice cleanup and certainly make sense for qemu-xen-unstable. cheers, Gerd