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] RE: Tmem vs order>0 allocation, workaround RFC

To: "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
Subject: [Xen-devel] RE: Tmem vs order>0 allocation, workaround RFC
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 16 Feb 2010 15:15:41 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, AndrewPeace <Andrew.Peace@xxxxxxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, kurt.hackel@xxxxxxxxxx, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, TimDeegan <Tim.Deegan@xxxxxxxxxxxxx>, Patrick Colp <pjcolp@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Grzegorz Milos <gm281@xxxxxxxxx>
Delivery-date: Tue, 16 Feb 2010 07:16:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <d2556e50-476d-487d-8fa8-aae67f63396c@default>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <2af13319-6b44-44e2-ab62-a0615208cf64@default> <C79F1B58.A196%keir.fraser@xxxxxxxxxxxxx> <78c49794-4454-4c3b-80a6-72efcbc73fb3@default><78c49794-4454-4c3b-80a6-72efcbc73fb3@default> <057c0f45-9c97-4b8a-8efa-1726fd951e19@default 4B7A6363020000780002F93C@xxxxxxxxxxxxxxxxxx><4B7A6363020000780002F93C@xxxxxxxxxxxxxxxxxx> <d2556e50-476d-487d-8fa8-aae67f63396c@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> 16.02.10 16:05 >>>
>Under what circumstances does dom0 require single-page-below-4G
>allocations?  Is it only for bounce buffers for PCI passthrough
>of old devices with 32-bit addressing limitations?  Or am I
>missing a much more common case?

Not just for pass-through; all devices only supporting 32-bit
addressing would have such requirements, and particularly common
ones are display adapters which have DRM/AGP drivers loaded for
them.

Jan


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