From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KNSc2-0005Bt-DZ for qemu-devel@nongnu.org; Mon, 28 Jul 2008 09:18:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KNSc0-0005AW-LX for qemu-devel@nongnu.org; Mon, 28 Jul 2008 09:18:05 -0400 Received: from [199.232.76.173] (port=49254 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KNSc0-0005AO-AQ for qemu-devel@nongnu.org; Mon, 28 Jul 2008 09:18:04 -0400 Received: from mx1.redhat.com ([66.187.233.31]:57990) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KNSbz-0000GP-Rv for qemu-devel@nongnu.org; Mon, 28 Jul 2008 09:18:04 -0400 From: Gerd Hoffmann Date: Mon, 28 Jul 2008 15:17:51 +0200 Message-Id: <1217251078-6591-1-git-send-email-kraxel@redhat.com> Subject: [Qemu-devel] [PATCH 0/7] merge some xen bits into qemu Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, xen-devel@lists.xensource.com Cc: Gerd Hoffmann Hi folks, Here are a bunch of patches which start adding xen support to qemu. Overview (individual patches have longer descriptions): #1 -- groundwork: build system, cmd line options, ... #2 -- xen backend driver infrastructrure #3 -- xen console backend driver #4 -- xen framebuffer backend driver #5 -- xen block backend driver #6 -- xen nic backend driver #7 -- allow xen disks and nics being configured via qemu command line options. With the first four patches in place upstream qemu can replace xen's qemu-dm for paravirtual domains. The block and nic backend drivers are full userspace implementations using the grant table device (gntdev). xen support is implemented using another machine type. xen's qemu-dm already uses the machine type to switch between paravirtualized and fully virtualized machines, so this was the natural choice. qemu has gets a new "xenpv" machine type additionally to the "pc" and "isapc" ones. I've placed the new files into the hw/ directory. With all my xen bits (partly not submitted yet with these patches) those add up to 18 new files, all prefixed with xen. Hmm, maybe I should better place them somewhere else, so the already quite crowded hw/ directory doesn't become even more cluttered? If so, any suggestions? New toplevel directory? New subdirectory below hw/? Something else? Comments? cheers, Gerd