From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=56452 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Oakqi-0004vR-9r
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 03:33:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1Oakqh-0003CY-7p
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 03:33:16 -0400
Received: from mx1.redhat.com ([209.132.183.28]:7842)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1Oakqh-0003CL-0q
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 03:33:15 -0400
Date: Mon, 19 Jul 2010 10:33:12 +0300
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Question about qemu firmware configuration
	(fw_cfg) device
Message-ID: <20100719073312.GY4689@redhat.com>
References: <20100717095059.GA19767@amd.home.annexia.org>
	<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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100719072802.GO13194@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 08:28:02AM +0100, Richard W.M. Jones wrote:
> On Mon, Jul 19, 2010 at 09:23:56AM +0300, Gleb Natapov wrote:
> > That what I am warring about too. If we are adding device we have to be
> > sure such device can actually exist on real hw too otherwise we may have
> > problems later.
> 
> I don't understand why the constraints of real h/w have anything to do
> with this.  Can you explain?
> 
Each time we do something not architectural it cause us troubles later.
So constraints of real h/w is our constrains to.

> > Also 1 second on 100M file does not look like huge gain to me.
> 
> Every second counts.  We're trying to get libguestfs boot times down
> from 8-12 seconds to 4-5 seconds.  For many cases it's an interactive
> program.
> 
So what about making initrd smaller? I remember managing two
distribution in 64M flash in embedded project.

--
			Gleb.