All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Guillermo Marcus <marcus@ti.uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmaping a kernel buffer to user space
Date: Tue, 31 Oct 2006 17:49:44 +0100	[thread overview]
Message-ID: <45477EA8.8060809@gmail.com> (raw)
In-Reply-To: <45477912.7070903@ti.uni-mannheim.de>

Guillermo Marcus wrote:
> Hi Jiri,
> 
> The fact that it does not works with RAM is well documented in LDD3,
> pages 430++. It says (and I tested) that remap_xxx_range does not work
> in this case. They suggest a method using nopage, similar to the one I
> implement.

Could somebody confirm, that this still holds?

> I do not see why remap_xxx_range has the limitation, but it is there.
> The question is then: can the limitation be removed, or can we implement
> a new function that maps RAM all at once without the need for a nopage
> implementation?
> 
> In any case, here is the code.

Hmm, interesting. I used remap_pfn_range for this purpose today and it worked (I
double-checked this). I should probably do the rework :(.

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
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-10-31 16:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31  9:19 mmaping a kernel buffer to user space Guillermo Marcus
2006-10-31 16:00 ` Jiri Slaby
2006-10-31 16:25   ` Guillermo Marcus
2006-10-31 16:49     ` Jiri Slaby [this message]
2006-10-31 17:08       ` Franck Bui-Huu
2006-10-31 19:44       ` Miguel Ojeda
2006-10-31 19:22   ` Russell King
2006-10-31 19:36     ` Jiri Slaby
2006-10-31 16:10 ` Rolf Offermanns
2006-10-31 16:33   ` Guillermo Marcus
2006-11-01 11:11 ` Rolf Offermanns
2006-11-01 12:58   ` Guillermo Marcus Martinez
2006-11-01 14:00     ` yogeshwar sonawane
2006-11-01 15:06       ` Guillermo Marcus Martinez
2006-11-02  8:31     ` Russell King
2006-11-02 11:31       ` Guillermo Marcus

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=45477EA8.8060809@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcus@ti.uni-mannheim.de \
    /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.