From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:52306)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Sx2TZ-00059t-CG
	for qemu-devel@nongnu.org; Thu, 02 Aug 2012 16:58:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Sx2TX-00028k-PS
	for qemu-devel@nongnu.org; Thu, 02 Aug 2012 16:58:33 -0400
Received: from mail-gg0-f173.google.com ([209.85.161.173]:57071)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Sx2TX-00028Y-LD
	for qemu-devel@nongnu.org; Thu, 02 Aug 2012 16:58:31 -0400
Received: by ggnp1 with SMTP id p1so8938828ggn.4
	for <qemu-devel@nongnu.org>; Thu, 02 Aug 2012 13:58:31 -0700 (PDT)
From: Anthony Liguori <anthony@codemonkey.ws>
In-Reply-To: <1343940385.6911.27.camel@pasglop>
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> <501A9A07.4040308@redhat.com>
	<1343940385.6911.27.camel@pasglop>
Date: Thu, 02 Aug 2012 15:58:28 -0500
Message-ID: <87d339f1u3.fsf@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [Qemu-devel] [PATCH 1/2] Allow QEMUMachine to override reset
	sequencing
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>, Paolo Bonzini <pbonzini@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>, agraf@suse.de, qemu-devel@nongnu.org

Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

> On Thu, 2012-08-02 at 17:17 +0200, Paolo Bonzini wrote:
>> 
>> 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.
>
> How does it do ? IE. how does it access a random pair of files on the
> host side ? Via some magic ports ?

Yes, see hw/fw_cfg.c

Regards,

Anthony Liguori

>
> Cheers,
> Ben.