>> >> Is anything on a driver to be able to tell when this is actually needed ? >> How will driver developers know? Can you add a bit of documentation to >> the API? If its transitive towards a secondary solution indicating so >> would help driver developers. > > I'll plug the io-mapping stuff again here, and more specifically the > userspace pte wrangling stuff we've added in 4.9 to i915_mm.c. Should > probably move that one to the core. That way io_mapping takes care of the > full reservartion, and allows you to on-demand kmap (for kernel) and write > ptes. All nicely fast and all, and for bonus, also nicely encapsulated. Yeah I think ideally we'd want to move towards that, however we don't tend to want to ioremap the full range even on 64-bit, which is what io-mapping does. At least on most GPUs with VRAM we rarely want to map VRAM for much, I think page tables and fbcon are probably the main two uses for touch it at all. So I don't think we need to be as efficient as i915 in this area. Dave. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
