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] [PATCH] Enable K8 GART as an IOMMU

To: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Enable K8 GART as an IOMMU
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 14 Feb 2007 10:04:54 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Feb 2007 02:04:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1449F58C868D8D4E9C72945771150BDFD965F6@xxxxxxxxxxxxxxxxx>
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: AcdPS5T881GBLwPSSluIANxcAsoqFgAeU4SwABar7us=
Thread-topic: [Xen-devel] [PATCH] Enable K8 GART as an IOMMU
User-agent: Microsoft-Entourage/11.3.3.061214
On 13/2/07 23:19, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx> wrote:

>>> /* Protected by balloon_lock. */
>>> -#define MAX_CONTIG_ORDER 9 /* 2MB */
>>> +#define MAX_CONTIG_ORDER 16 /* 256MB */
>>> static unsigned long discontig_frames[1<<MAX_CONTIG_ORDER];
>>> static multicall_entry_t cr_mcl[1<<MAX_CONTIG_ORDER];
>> 
>> This seems dangerous to me.
> 
> We need at least 64MB of contiguous memory for the aperture.

Not that I know anything much about the K8 GART, but I assume the aperture
is an address range that the GART takes control of and dynamically aliases
other RAM pages into? Is it necessary to burn 64MB of RAM (which is
presumably inaccessible when the GART is turned on)? Will the BIOS not
already have conveniently piointed the aperture into a RAM hole (e.g., just
below 4GB)?

 -- Keir



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