From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=34234 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Oalu2-0005Tu-N8
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 04:40:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1Oalu1-0005ry-Hs
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 04:40:46 -0400
Received: from mx1.redhat.com ([209.132.183.28]:10402)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1Oalu1-0005rm-8c
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 04:40:45 -0400
Date: Mon, 19 Jul 2010 11:40:41 +0300
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Question about qemu firmware configuration
	(fw_cfg) device
Message-ID: <20100719084041.GH4689@redhat.com>
References: <20100717095353.GB19767@amd.home.annexia.org>
	<269D196D-8CE8-4E24-8EE1-39756AC55F7F@suse.de>
	<20100718200942.GL13194@amd.home.annexia.org>
	<44FD4F00-843D-41C8-B21A-148D16745015@suse.de>
	<20100719062356.GU4689@redhat.com>
	<20100719072802.GO13194@amd.home.annexia.org>
	<20100719073312.GY4689@redhat.com>
	<20100719074416.GP13194@amd.home.annexia.org>
	<20100719075533.GC4689@redhat.com>
	<20100719083411.GR13194@amd.home.annexia.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100719083411.GR13194@amd.home.annexia.org>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org

On Mon, Jul 19, 2010 at 09:34:11AM +0100, Richard W.M. Jones wrote:
> On Mon, Jul 19, 2010 at 10:55:33AM +0300, Gleb Natapov wrote:
> > Why not put then on cdrom or disk?
> 
> It simplifies device and mountpoint enumeration not to have a separate
> disk.  It would also mean we couldn't use standard Fedora paths, or
> we'd have to have bind-mount /bin etc on to the disk mount point,
> which again complicates things.
> 
Can't help you here, but if it's doable you can speedup your startup
time much more then by a second.

> Anyway, what we're talking about here is a problem in qemu.  How is
The problem is that you want to speed up your application. There is more
then one solution to the problem. If you come up with reasonable
solution in qemu that it OK. 

> making initrd loading faster not a benefit for everyone?  Every boot
> has to load an initrd of some size, so making that operation faster
> benefits every user, even if individually only by a small amount.
> 
Most users load initrd from a disk not by -initrd option.

--
			Gleb.