From: c.seitz@tu-bs.de (Christoph Seitz)
To: kernelnewbies@lists.kernelnewbies.org
Subject: User space memory
Date: Sun, 10 Mar 2013 19:00:27 +0100 [thread overview]
Message-ID: <513CCA3B.3020102@tu-bs.de> (raw)
Hi all,
I have some problems allocation Memory the right way and use it in my
kernel module.
I use a char device for reading and writing from/to a pcie dma card.
Especially the read function makes me some headache. The user allocates
some memory with posix_memalign and call the read function on the
device, so that the devices knows where to write to. My driver now uses
get_user_pages() to pin the user pages. The memory has never been
written or read by the user, so it's not yet in the RAM, right? And
get_user_pages returns a valid number of pages, but for every page the
same struct. (respectively the same pointer). Is there any way to ensure
that the user pages are in the ram and get_user_pages returns a valid
page array?
Regards
Chris
next reply other threads:[~2013-03-10 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 18:00 Christoph Seitz [this message]
2013-03-12 13:08 ` User space memory Prabhu nath
2013-03-12 14:03 ` Christoph Seitz
2013-03-12 17:18 ` Valdis.Kletnieks at vt.edu
2013-03-12 14:29 ` Valdis.Kletnieks at vt.edu
2013-03-13 5:18 ` Prabhu nath
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=513CCA3B.3020102@tu-bs.de \
--to=c.seitz@tu-bs.de \
--cc=kernelnewbies@lists.kernelnewbies.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).