From: Andrew Morton <akpm@osdl.org>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Any reason why install_page and zap_page_range are not exported?
Date: Thu, 31 Jul 2003 15:16:11 -0700 [thread overview]
Message-ID: <20030731151611.0dc69bf9.akpm@osdl.org> (raw)
In-Reply-To: <8D43EFF35A6@vcnet.vc.cvut.cz>
"Petr Vandrovec" <VANDROVE@vc.cvut.cz> wrote:
>
> 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 :-(
Agree, install_page() should be exported. I'll submit a patch.
> 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.
zap_page_range() sounds like an odd thing to be exporting. If we had an
in-kernel module which needed it then OK. Do you have plans in that
direction?
prev parent reply other threads:[~2003-07-31 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 21:03 Any reason why install_page and zap_page_range are not exported? Petr Vandrovec
2003-07-31 22:16 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030731151611.0dc69bf9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).