From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46662) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Swx9g-0006H1-KV for qemu-devel@nongnu.org; Thu, 02 Aug 2012 11:17:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Swx9a-0003Bo-To for qemu-devel@nongnu.org; Thu, 02 Aug 2012 11:17:40 -0400 Received: from mail-wg0-f53.google.com ([74.125.82.53]:45551) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Swx9a-0003Bc-NJ for qemu-devel@nongnu.org; Thu, 02 Aug 2012 11:17:34 -0400 Received: by wgbfm10 with SMTP id fm10so6479883wgb.10 for ; Thu, 02 Aug 2012 08:17:34 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <501A9A07.4040308@redhat.com> Date: Thu, 02 Aug 2012 17:17:27 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1343873409-8571-1-git-send-email-david@gibson.dropbear.id.au> <1343873409-8571-2-git-send-email-david@gibson.dropbear.id.au> <87vch2nhn0.fsf@codemonkey.ws> <1343879428.6911.6.camel@pasglop> In-Reply-To: <1343879428.6911.6.camel@pasglop> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/2] Allow QEMUMachine to override reset sequencing List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Benjamin Herrenschmidt Cc: David Gibson , agraf@suse.de, Anthony Liguori , qemu-devel@nongnu.org Il 02/08/2012 05:50, Benjamin Herrenschmidt ha scritto: > >> > This sort of stuff is either >> > (1) hard coded in a firmware/flashrom or (2) built dynamically in >> > firmware. Let's not pretend like we're doing this because it's needed >> > for real hardware. > Doesn't matter, we do things like -kernel which means pre-loading the > kernel from qemu, even on x86. That doesn't match real HW either, but > it's convenient to have. But overall there are real HW reasons to > control the reset as well so the hook makes sense both ways. On x86 we do not pre-load the kernel. Neither the kernel/initramfs and the option ROM that loads the kernel are written in memory, they are passed to the guest via fw_cfg. Then the option ROM is loaded by the BIOS, and loads the kernel/initramfs. Paolo