From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=50361 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oarhp-00082C-Db for qemu-devel@nongnu.org; Mon, 19 Jul 2010 10:52:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oarho-0002YH-5U for qemu-devel@nongnu.org; Mon, 19 Jul 2010 10:52:33 -0400 Received: from mail-pz0-f45.google.com ([209.85.210.45]:61526) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oarho-0002Y2-18 for qemu-devel@nongnu.org; Mon, 19 Jul 2010 10:52:32 -0400 Received: by pzk10 with SMTP id 10so1594845pzk.4 for ; Mon, 19 Jul 2010 07:52:30 -0700 (PDT) Message-ID: <4C4466A7.3030808@codemonkey.ws> Date: Mon, 19 Jul 2010 09:52:23 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Question about qemu firmware configuration (fw_cfg) device References: <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> <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> In-Reply-To: <20100719091543.GM4689@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel@nongnu.org, Alexander Graf , "Richard W.M. Jones" 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. Regards, Anthony Liguori > Honestly I would expect much > greater speedup from Richard's approach like 2 seconds vs 8 seconds. It > is hard to justify code complication just for 1 second speedup. > > -- > Gleb. > >