From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKv78-0000LN-Ff for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:44:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKv73-0000Fv-Oq for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:44:29 -0500 Received: from [199.232.76.173] (port=60489 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKv73-0000Fk-D2 for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:44:25 -0500 Received: from mx1.redhat.com ([209.132.183.28]:9414) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKv72-0003FJ-Rc for qemu-devel@nongnu.org; Wed, 16 Dec 2009 09:44:25 -0500 Date: Wed, 16 Dec 2009 16:41:33 +0200 From: "Michael S. Tsirkin" Subject: Re: Proper support for PCI-based option rom loading (was Re: [Qemu-devel] Re: qdev property bug?) Message-ID: <20091216144131.GA29759@redhat.com> References: <20091214203603.GJ6150@redhat.com> <4B26A3B2.2030006@codemonkey.ws> <20091214205141.GC6398@redhat.com> <4B26F678.4010603@codemonkey.ws> <4B27541F.9020603@redhat.com> <4B276197.1080606@redhat.com> <4B27E518.7060300@codemonkey.ws> <20091215211715.GF26712@redhat.com> <4B28026E.4060100@codemonkey.ws> <4B28F192.4080807@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B28F192.4080807@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: Chris Wright , glommer@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, Alexander Graf , Kevin O'Connor , Sebastian Herbszt On Wed, Dec 16, 2009 at 03:41:22PM +0100, Gerd Hoffmann wrote: > On 12/15/09 22:41, Anthony Liguori wrote: >> BTW, I'm pretty sure this style of option rom loading (from a PCI >> device) is going to be required for device passthrough if we want to >> support running those roms in the guests. > > Well, qemu-kvm has quite some code to poke the rom out of /proc/bus/pci > and feed it into the rom loader. All this can simply be dropped then. > > cheers > Gerd It's probably safer not to assume that guest does not run the rom directly. -- MST