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

[Xen-devel] linux: GFP_DMA/GFP_DMA32

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] linux: GFP_DMA/GFP_DMA32
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 03 Apr 2007 15:34:51 +0100
Delivery-date: Tue, 03 Apr 2007 07:32:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
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?

Thanks, Jan

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

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