From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=45869 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OgaFv-000408-1x for qemu-devel@nongnu.org; Wed, 04 Aug 2010 05:27:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OgaFq-0000ET-E4 for qemu-devel@nongnu.org; Wed, 04 Aug 2010 05:27:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:31708) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OgaFq-0000EN-2q for qemu-devel@nongnu.org; Wed, 04 Aug 2010 05:27:18 -0400 Date: Wed, 4 Aug 2010 12:27:13 +0300 From: Gleb Natapov Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35? Message-ID: <20100804092713.GD10499@redhat.com> References: <4C5854F1.3000905@codemonkey.ws> <4C5858B2.9090801@redhat.com> <4C585F5B.5070502@codemonkey.ws> <4C58635B.7020407@redhat.com> <20100803190525.GB16570@redhat.com> <4C586AB9.5040302@codemonkey.ws> <4C586CF9.7030206@redhat.com> <20100803220628.GC28523@amd.home.annexia.org> <4C59009B.1050500@redhat.com> <20100804092428.GD28523@amd.home.annexia.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100804092428.GD28523@amd.home.annexia.org> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Richard W.M. Jones" Cc: kvm@vger.kernel.org, Avi Kivity , qemu-devel@nongnu.org On Wed, Aug 04, 2010 at 10:24:28AM +0100, Richard W.M. Jones wrote: > On Wed, Aug 04, 2010 at 08:54:35AM +0300, Avi Kivity wrote: > > On 08/04/2010 01:06 AM, Richard W.M. Jones wrote: > > >On Tue, Aug 03, 2010 at 10:24:41PM +0300, Avi Kivity wrote: > > >>Why do we need to transfer roms? These are devices on the memory > > >>bus or pci bus, it just needs to be there at the right address. > > >>Boot splash should just be another rom as it would be on a real > > >>system. > > >Just like the initrd? > > > > There isn't enough address space for a 100MB initrd in ROM. > > Because of limits of the original PC, sure, where you had to fit > everything in 0xa0000-0xfffff or whatever it was. > > But this isn't a real PC. > In what way it is not? > You can map the read-only memory anywhere you want. > You can't. Guests expects certain memory layouts. -- Gleb.