From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] Don't explicitly set BAR values for VMware VGA Date: Sun, 24 Feb 2008 09:09:18 +0200 Message-ID: <47C1181E.6010304@qumranet.com> References: <1203709210-23314-1-git-send-email-aliguori@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, Andrzej Zaborowsi , qemu-devel@nongnu.org To: Anthony Liguori Return-path: In-Reply-To: <1203709210-23314-1-git-send-email-aliguori@us.ibm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Anthony Liguori wrote: > Right now we set explict base addresses for the PCI IO regions in the VMware > VGA device. We don't register the second region at all and instead directly > map the physical memory. > > The problem is, the addresses we're setting in the BAR is not taken into > account in the e820 mapping. > > This patch removes the explicit BARs and registers the second region through > the normal PCI code. > > I've only tested with a Linux guest and the open source VMware VGA driver. > > This patch needs -p2 to apply against the QEMU CVS tree. > > Since it seems like qemu will apply this soon, I'll pick it up via the next merge. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/