On Iau, 2005-07-07 at 23:50, Thomas Hellström wrote: > 1.) get_user_pages() should presumably lock a page into physical memory. > Will this always cause a segfault for an invalid address?
You'll get an error for invalid space. You may also get null entries in the array for locking the paged if they relate to a hole in memory. > 2.) Unlocking pages previously locked with get_user_pages(): is > page_cache_release() sufficient or are more calls needed? Could the > unlocking functions be called from an interrupt handler? Is a refcount > maintained for this page locking or is it one-level only? It is refcounted. > 3.) Is memory allocated with vmalloc always locked into physical memory > until freed? Yes but it may not be DMAable. ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
