-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephane Marchesin wrote: > Stephane Marchesin wrote: > >> Now, there is one question that sounds to me like it will have >> implications over the whole memory manager design : do we want to >> enforce video memory ownership ? > > Ok, here is what came out of the irc meeting : > - we don't need to enforce video memory ownership, but the drm needs to > be able to track allocation owners anyway, for example if a process dies > unexpectedly.
Correct. The kernel can do that tracking via the log. Each process gets a block of region IDs from the kernel. Each time a process makes an allocation, it writes the offset, size, and ID to the log. > - regions that are marked as "preserve" have a matching backing store > region in system ram. That region is made of pinned pages. Okay. There are also regions that are maked as 'pinned'. The only regions that should need this marking are memory areas that are being scanned out (e.g., cursor, current front buffer, etc.) by the video hardware. We'll eventually want to be able to move those regions, but I think we can skip that for now. The thing that killed this project for me the first time around was trying to tackle everything all at once. I've been told that I have a big mouth, but I can only bite off so much at once. ;) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDC1MvX1gOwKyEAw8RAvz9AJ9pd2Wy7B6rgV72n/Tb3ipdhZPIgQCfXfar WOxN/CBydERASH8ZDFocmlQ= =yx/R -----END PGP SIGNATURE----- ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
