All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: sasha <sasha@scalemp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Map memory to user, then map it back to kernel
Date: Wed, 09 Aug 2006 16:31:28 +0159	[thread overview]
Message-ID: <44D9F1D7.7050407@gmail.com> (raw)
In-Reply-To: <44D98BF3.5060706@scalemp.com>

sasha wrote:
> Hi folks.
> 
> I am looking for a way to map a memory (allocated with get_free_pages()) 
> from kernel space to user space, so that I will later be able to map it 
> back with get_user_pages().
> 
> I tried remap_pfn_range(), but it didn't work as it assumes the memory 
> being mapped is IO range (marking vma with VM_IO flag), while 
> get_user_pages() works on regular memory.
> 
> Any ideas?

VM_IO flag means not to swap this memory and don't do any side-effects bound 
with that IIRC.

If you want to mmap some memory in kernel to allow userspace to be able to read 
from it, just remap and don't care. I actually don't understand, what you mean 
by remapping it back to kernelspace, can you be more specific?

Caveat of get_free_pages is that it allocates physically contiguous memory and 
this may fail in later times, when the memory is not so free. You can use 
virtual memory to avoid this: vmalloc_32_user, remap_vmalloc_range, vfree.

regards,
-- 
<a href="http://www.fi.muni.cz/~xslaby/">Jiri Slaby</a>
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

      reply	other threads:[~2006-08-09 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09  7:17 Map memory to user, then map it back to kernel sasha
2006-08-09 14:32 ` Jiri Slaby [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=44D9F1D7.7050407@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sasha@scalemp.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.