On Fri, 2007-12-21 at 14:01 +0100, Thomas Hellström wrote: > This looks like a good thing, but is there a way we can avoid doing this > in the ttm backend? > Some backends (Poulsbo, and I think Dave's work on Radeon) implement a > null populate() function and use the ttm page array directly. > > Hence we could perhaps use the dummy page in the ttm page directly, > like the user bo/ttm objects. That way we would also save a lot of ttm > backend code.
I need to leave the CPU-visible page table blank so that writes from the process will fault in a real page. I don't know how to do that without keeping the ttm page list empty for these replaced pages. Also, if we leave objects mapped to both CPU and GTT (as we should be able to do), we'd have to invalidate the GTT mapping when the CPU faulted in a new page. This may be harder than I thought. However, a larger issue at this point is making TTM buffer objects pageable -- with unpageable objects, I cannot make the X server use them for pixmaps yet as firefox would destroy your machine even faster. I suspect fixing that will have a fairly widespread effect on pagemapping throughout the DRM, so it might be best to start there with an eye to allowing dummy page mapping in the GTT. -- [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
