Keith Packard wrote: > > >> The other approach is to use one address space per device. >> > > This would require constructing an entirely artificial linear space for > my objects. You then have to track this per-device linear address for > each object and pass that into the mmap call. And, what does it mean > when you ask to mmap a range spanning multiple objects? > That's clearly an illegal operation and would return an error. > >> 1) Hack ptes from the driver. >> > > Nope, not doing this; the GTT-based mapping would allocate separate PTEs > using the existing standard device mapping APIs. > > But what happens when you unbind an object from the GTT while you map that data through the GTT? In your original email you stated that you'd walk through the VMAs and modify the PTEs.
If you want to avoid that, you need to run unmap_mapping_range() on an address space. What address space would that be? /Thomas ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
