Kristian Høgsberg wrote: >On 12/19/06, Thomas Hellström <[EMAIL PROTECTED]> wrote: > > >>Dave Airlie wrote: >> >> >> >>>>Does anbody know why drm is using vmalloc_32 instead of vmalloc when >>>>allocating SHM maps? >>>> >>>> >>>I may be wrong but maybe for mixed 64/32-bit kernel/userspace systems, did >>>it ever use vmalloc? >>> >>> >>> >>Don't know really, but since drm AFAICT never cares about the physical >>address of the >>underlying pages, vmalloc should probably do just fine, or even better >>vmalloc_user on newer kernels, >>=> we could skip the memset() i just added. >> >> > >AFAIK, vmalloc_32 put the memory in the lower 4gb, so it's accessible >by peripherals that only support 32-bit DMA. If that's not an issue, >there's no need to use the _32 version. > >Kristian > > Thanks, Kristian. I've already changed to vmalloc_user in git. It's for SAREAs only, and they will hopefully never get submitted to the hardware.
/Thomas >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys - and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >-- >_______________________________________________ >Dri-devel mailing list >Dri-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/dri-devel > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
