From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MxMEh-0004HG-0l for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:50:55 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MxMEc-0004DM-Ao for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:50:54 -0400 Received: from [199.232.76.173] (port=39778 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MxMEc-0004DH-8G for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:50:50 -0400 Received: from mx1.redhat.com ([209.132.183.28]:1025) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MxMEb-0002GG-O4 for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:50:50 -0400 Message-ID: <4AD3423B.3020908@redhat.com> Date: Mon, 12 Oct 2009 16:50:35 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 2/3] qemu: make cirrus init value pci spec compliant References: <20091008145241.GC12275@redhat.com> <4ACE0559.5040206@redhat.com> <20091008160623.GA13710@redhat.com> <4ACE0FC6.3050908@redhat.com> <20091008184011.GA6576@shareable.org> <20091009064359.GA9942@redhat.com> <20091009070049.GG19692@redhat.com> <20091009101259.GA12027@redhat.com> <20091009114903.GI19692@redhat.com> <4AD3330B.4090506@redhat.com> <20091012135318.GB3026@redhat.com> In-Reply-To: <20091012135318.GB3026@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: Anthony Liguori , kvm-devel , "Michael S. Tsirkin" , "qemu-devel@nongnu.org" , Avi Kivity On 10/12/09 15:53, Gleb Natapov wrote: > On Mon, Oct 12, 2009 at 03:45:47PM +0200, Gerd Hoffmann wrote: >>>>>> We should fix qemu to re-read bios from flash. >>>>>> Makes sense? >>>>>> >>>>> We have option_rom_setup_reset() already. >>>> >>>> We don't, anymore :) >>> We are fast! Well, we surely have something similar instead. >> >> Sure. Try 'info roms'. Everything listed there will be reloaded on >> reset (unless mem=rom, in which case the guest should not be able to >> modify the bits in the first place). That includes vgabios, >> optionroms, -kernel images, ... >> > And what about bios? I don't see it there. pc.c does some magic here to map the complete bios into high memory and the legacy part at 0xe0000, thats why it is loaded in a different way. It gets loaded to IO_MEM_ROM memory though, so the guest should not be able to corrupt it. cheers, Gerd