lkml.org 
[lkml]   [2003]   [Jul]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectAny reason why install_page and zap_page_range are not exported?
Hi,
in one of my projects I found that what we were doing in 2.2.x/2.4.x
with strange hacks to mmap & nopage methods to get non-linear
mappings from some device can be done in 2.[56].x with remap_file_pages.

Only two things are missing: install_page is not exported for modules,
so it is not possible to create own vma's populate function, as
there is no way how to put some page into pagetables. Or at least
I did not found such - even if I'll copy install_page's code to the
module, I'll just run to the other non-exported symbols :-(

And second missing thing is zap_page_range - we need way to tell
that specified page is not mapped anywhere (mostly for debugging
purposes). At worst install_page with PROT_NONE protection can be
used for that, but it seems natural that if there should be no page
there, we should just put nothing to the pagetables instead of some
fake page. And for large ranges doing one 200MB zap_page_range is
much faster than doing 50000 install_pages.

Is it intentional that these functions are not exported for modules,
or is it just case that nobody needed such functions yet?
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:47    [W:0.042 / U:0.092 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site