>>> Jeremy Fitzhardinge <jer...@goop.org> 05.10.09 21:09 >>> >vmalloc_32 is a general problem. The only clean way I can see to make >it work under Xen is to make sure all the pages in the DMA32 zone are >really under 4G in machine addresses. But that doesn't scale very well
Why? Just adding a hook in vmalloc.c would do. >if you have more than one domain wanting to use vmalloc_32 for hardware >access (or a few small domains). That's why noted that doing this for the whole zone is likely overkill. >I'm wondering if the "proper" fix is to introduce a vmalloc_dma() call >which allocates the pages with the proper DMA API calls them maps them >together in the vmalloc space, and then start migrating drivers over to >this new API (ie as needed when people report Xen problems). That would >be more generally correct, but perhaps it would be a bit more cumbersome >because it would have to return both the vaddr of the vmapping, and the >dma_addr_t array, so that vfree_dma() can make the proper >dma_free_coherent calls. Hmm, yes, but the more cumbersome an API is to use, the less likely it is that people would want to adopt using it (or that it would be mergable in the first place)). Jan ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
