WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] allocating AGP aperture memory

To: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] allocating AGP aperture memory
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 18 Oct 2005 23:17:03 +0100
Delivery-date: Tue, 18 Oct 2005 22:14:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXUItEVdqWcbj10TmOmktd1+s3AmQADf3OQ
Thread-topic: [Xen-devel] allocating AGP aperture memory
> I'm still working on getting IOMMU support for Opterons under Xen.
> 
> During the boot sequence, Dom0 is finding the aperture 
> through the AGP controller at address 0xe8000000 like it 
> should.  During AGP controller initialization, though, it 
> fails to reserve the address space because the necessary 
> pages are PageReserved in the mem_map.

Trying to looks a bus (machine) address up in dom0's mem_map
(pseudo-physical) won't yield anything sensible.

Presumably the driver isn't expecting to find memory behind the
aperture? Is it just trying to reserve the bus address range for
purposes of ensuring that other PCI devices don't get allocated to it? 

Ian
 
> I'm not sure where the pages are being reserved, or even if 
> mem_map for dom0 is completely valid, or if I should be 
> handling this through the hypervisor.  Any comments or suggestions?
> 
> -Mark Langsdorf
> AMD, Inc.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel