From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=33895 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Oas8D-0002bs-KX
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 11:19:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1Oarjz-0002uq-Vv
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 10:54:49 -0400
Received: from mx1.redhat.com ([209.132.183.28]:51012)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1Oarjz-0002uk-NZ
	for qemu-devel@nongnu.org; Mon, 19 Jul 2010 10:54:47 -0400
Date: Mon, 19 Jul 2010 17:54:45 +0300
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Question about qemu firmware configuration
	(fw_cfg) device
Message-ID: <20100719145445.GW4689@redhat.com>
References: <20100719073312.GY4689@redhat.com>
	<20100719074416.GP13194@amd.home.annexia.org>
	<20100719075533.GC4689@redhat.com>
	<20100719083411.GR13194@amd.home.annexia.org>
	<20100719084041.GH4689@redhat.com>
	<20100719090004.GS13194@amd.home.annexia.org>
	<20100719090654.GK4689@redhat.com>
	<9C4457B3-884D-482D-9BD0-C49AA20FB3CF@suse.de>
	<20100719091543.GM4689@redhat.com> <4C4466A7.3030808@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C4466A7.3030808@codemonkey.ws>
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>, "Richard W.M. Jones" <rjones@redhat.com>

On Mon, Jul 19, 2010 at 09:52:23AM -0500, Anthony Liguori wrote:
> On 07/19/2010 04:15 AM, Gleb Natapov wrote:
> >On Mon, Jul 19, 2010 at 11:09:13AM +0200, Alexander Graf wrote:
> >>On 19.07.2010, at 11:06, Gleb Natapov wrote:
> >>
> >>>On Mon, Jul 19, 2010 at 10:00:04AM +0100, Richard W.M. Jones wrote:
> >>>>virt-install is another program that uses explicit -initrd.
> >>>>
> >>>Installation takes a lot of time. Saving 1 second there will not be
> >>>noticeable. And during lifetime of installed VM initrd will be loaded
> >>>from its disk.
> >>Guys, please. It shouldn't be one or the other. Let's make sure both ways of doing things are fast. That's what users want: fast.
> >>
> >That what we are talking about, no? We are trying to find faster way to
> >load kernel/initrd and stay architectural.
> 
> Modern platforms are not nearly as "architectural" as you would think.
> 
> It's not unusual to hang a custom chip off of the Southbridge that
> implements platform specific services along with an array of
> "legacy" devices that are implemented mostly in software to cost.
> 
> Other buses (like PS/2) are largely implemented in SMM today by the BIOS.
> 
I don't get your point. What is not "architectural" about all that?

--
			Gleb.