From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=34570 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OggmE-0006Vb-Rx for qemu-devel@nongnu.org; Wed, 04 Aug 2010 12:25:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OggmD-0001jC-Tr for qemu-devel@nongnu.org; Wed, 04 Aug 2010 12:25:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:1025) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OggmD-0001io-MU for qemu-devel@nongnu.org; Wed, 04 Aug 2010 12:25:09 -0400 Message-ID: <4C59945C.8000808@redhat.com> Date: Wed, 04 Aug 2010 19:25:00 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35? References: <20100803162857.GX13789@amd.home.annexia.org> <4C584781.9040609@redhat.com> <4C5847CD.9080107@codemonkey.ws> <4C5848C7.3090806@redhat.com> <4C584982.5000108@codemonkey.ws> <4C584B66.5070404@redhat.com> <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> <4C588804.5060803@redhat.com> <4C590046.2020705@redhat.com> <4C591D48.9080301@redhat.com> <4C592218.3000901@redhat.com> <4C596549.1070109@codemonkey.ws> In-Reply-To: <4C596549.1070109@codemonkey.ws> 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: Anthony Liguori Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Gerd Hoffmann , Gleb Natapov , "Richard W.M. Jones" On 08/04/2010 04:04 PM, Anthony Liguori wrote: > On 08/04/2010 03:17 AM, Avi Kivity wrote: >> For playing games, there are three options: >> - existing fwcfg >> - fwcfg+dma >> - put roms in 4GB-2MB (or whatever we decide the flash size is) and >> have the BIOS copy them >> >> Existing fwcfg is the least amount of work and probably satisfactory >> for isapc. fwcfg+dma is IMO going off a tangent. High memory flash >> is the most hardware-like solution, pretty easy from a qemu point of >> view but requires more work. > > The only trouble I see is that high memory isn't always available. If > it's a 32-bit PC and you've exhausted RAM space, then you're only left > with the PCI hole and it's not clear to me if you can really pull out > 100mb of space there as an option ROM without breaking something. > 100MB is out of the question, certainly. I'm talking about your isapc problem, not about a cdrom replacement. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.