From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MIlIx-0004mM-FN for qemu-devel@nongnu.org; Mon, 22 Jun 2009 11:19:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MIlIs-0004l6-W4 for qemu-devel@nongnu.org; Mon, 22 Jun 2009 11:19:30 -0400 Received: from [199.232.76.173] (port=47334 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MIlIs-0004l3-QC for qemu-devel@nongnu.org; Mon, 22 Jun 2009 11:19:26 -0400 Received: from mail-pz0-f185.google.com ([209.85.222.185]:62571) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MIlIs-0003Ok-EL for qemu-devel@nongnu.org; Mon, 22 Jun 2009 11:19:26 -0400 Received: by pzk15 with SMTP id 15so2646489pzk.4 for ; Mon, 22 Jun 2009 08:19:25 -0700 (PDT) Message-ID: <4A3FA0F7.7030604@codemonkey.ws> Date: Mon, 22 Jun 2009 10:19:19 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/4] Add multiboot support (x86) v3 References: <1245326201-17019-1-git-send-email-agraf@suse.de> <4A3F93B2.1050407@codemonkey.ws> <73F251E4-3A8B-4CA8-8523-94AEA34FEEDC@suse.de> In-Reply-To: <73F251E4-3A8B-4CA8-8523-94AEA34FEEDC@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: kwolf@redhat.com, rene@exactcode.de, qemu-devel@nongnu.org Alexander Graf wrote: > > On 22.06.2009, at 16:22, Anthony Liguori wrote: > >> Alexander Graf wrote: >>> This patch implements support for Multiboot on x86 for -kernel. >>> Multiboot is a "new" approach to get rid of different bootloaders, >>> providing >>> a unified interface for the kernel. It supports command line options >>> and >>> kernel modules. >>> >> >> Works booting Xen from Fedora 8 and doesn't regress -kernel. >> >> However, when using multiboot, the ROMs don't survive a reboot. If >> you look at how -kernel is implemented, you'll various calls >> option_rom_reset() to cover not just the roms but also the >> kernel/initrd bits. You'll need to do the same thing for multiboot. > > Does -kernel with a Linux kernel survive a reboot? Yes. > Also, do we still want to use the -kernel after a reboot or rather go > through the normal boot order? We want -kernel to keep working. > Is there an easy way to get a callback when we get #reset? qemu_register_reset(). But you very likely want to use option_rom_reset(). Regards, Anthony Liguori