From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: qemu oddness with isolinux vesamenu.c32 Date: Mon, 21 Jul 2008 12:43:08 +0300 Message-ID: <48845A2C.4050306@qumranet.com> References: <48800A9D.1080403@zytor.com> <4880C3F3.6010202@zytor.com> <488199AB.4020109@qumranet.com> <488232A4.1010706@zytor.com> <488298A3.9050502@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Matt_Domsch@Dell.com, pjones@redhat.com, kvm@vger.kernel.org, Anthony Liguori To: "H. Peter Anvin" Return-path: Received: from il.qumranet.com ([212.179.150.194]:27274 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755353AbYGUJnJ (ORCPT ); Mon, 21 Jul 2008 05:43:09 -0400 In-Reply-To: <488298A3.9050502@zytor.com> Sender: kvm-owner@vger.kernel.org List-ID: H. Peter Anvin wrote: > H. Peter Anvin wrote: >> >> Yes, although simulating the memory "pre-shadowed" works just as >> well; then it should be marked readonly by the BIOS immediately prior >> to running INT 19h. >> > > On top of this, getting proper DDIM support and PCI expansion ROM into > the BIOS would be a good thing. A PCI expansion ROM is attached to a > PCI device as a BAR and mapped into high memory, it is then copied to > shadowed RAM by the BIOS and its initialization stub is run. This is > done one device at a time, so that the initialization code can be > discarded, per the DDIM spec. I imagine it's necessary for proper pci device assignment. -- error compiling committee.c: too many arguments to function