On Wed, Aug 22, 2012 at 04:45:45PM +0100, Chris Wilson wrote: > On Mon, 20 Aug 2012 23:17:06 +0200, Daniel Vetter <[email protected]> wrote: > > On Sat, Aug 11, 2012 at 03:41:26PM +0100, Chris Wilson wrote: > > > Signed-off-by: Chris Wilson <[email protected]> > > > > Since most of the overlay-supporting hw uses physical mem for the overlay > > I think this isn't much worth it: The additional frobbery in > > attach/detach_phys object is likely more work than we'll anything we'll > > ever gain from using stolen mem here. Especially since we'll use stolen > > mem already for the rings. > > In a straw poll of the machines on my desk, non-physical machines outnumber > the physical overlay machines. :-p > > However, hooking up the physical to use stolen is also a good idea. Too > bad, I haven't found a way to detect the base of stolen memory on gen2 > devices without arch specific internals. It worked nicely right up until > I tried to build i915.ko as a module.
Hm, can't we make a case to EXPORT_GPL that memmap? -Daniel -- Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
