Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] drm

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] drm
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 27 Feb 2007 09:45:55 +0000
Delivery-date: Tue, 27 Feb 2007 01:46:13 -0800
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 see that the example kernel configs have drm generally enabled
(obviously except for the xenU ones, though I'm a little surprised ia64's
has this on), looking at the sources makes me wonder if this (specifically
the interaction with AGP) has really been tested. There's a very
suspicious use of pte_pfn() in there (this is what actually caught my
attention the other day when doing something entirely unrelated), two
__va() instances that appear to take bus addresses as input, and two
questionable virt_to_phys() ones.

Jan

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

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