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] linux: GFP_DMA/GFP_DMA32

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] linux: GFP_DMA/GFP_DMA32
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 04 Apr 2007 08:11:18 +0100
Delivery-date: Wed, 04 Apr 2007 00:09:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4612822B.76E4.0078.0@xxxxxxxxxx>
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: Acd2iHCYrxA9BuJ7EduKZAAWy6hiGQ==
Thread-topic: [Xen-devel] linux: GFP_DMA/GFP_DMA32
User-agent: Microsoft-Entourage/11.3.3.061214
How many callers rely on GFP_DMA32? We gave up on GFP_DMA because no halfway
modern hardware relies on it and we can't currently satisfy requests for
memory below 16MB anyway.

As for solutions, either we have to hook the memory allocator somehow to get
a call out to allocate memory of the correct type, or callers do indeed need
fixing one by one.

 -- Keir

On 3/4/07 15:34, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> While I have a patch queued to address related issues in intel-agp, a quick
> scan
> of the Linux tree seems to reveal several more cases where assumptions are
> being made on GFP_DMA{,32} allocations - either the result (even properly
> passed through virt_to_bus()) is put into hardware registers (with no
> guarantee that it fits the width required by those registers or fields
> thereof),
> or page-crossing arithmetic is being done (explicitly or implicitly). All this
> is set
> to cause data corruption.
> 
> Are there any ideas, other than either suppressing such components or fixing
> them one by one, how to address this problem?



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

<Prev in Thread] Current Thread [Next in Thread>