From: Timur Tabi <timur.tabi@ammasso.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernelnewbies@nl.linux.org
Subject: Re: get_user_pages() still broken in 2.6
Date: Wed, 29 Sep 2004 09:46:38 -0500 [thread overview]
Message-ID: <415ACACE.1020008@ammasso.com> (raw)
In-Reply-To: <1096413678.16198.16.camel@localhost>
Dave Hansen wrote:
> You probably want mlock(2) to keep the kernel from messing with the ptes
> at all.
mlock() can only be called via sys_mlock(), which is a user-space call.
Not only that, but only root can call sys_mlock(). This is not
compatible with our needs.
> But, you should probably really be thinking about why you're
> accessing the page tables at all. I count *ONE* instance in drivers/
> where page tables are accessed directly.
I access PTEs to get the physical addresses of a user-space buffer, so
that we can DMA to/from it directly.
--
Timur Tabi
Staff Software Engineer
timur.tabi@ammasso.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-09-29 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 22:40 Timur Tabi
2004-09-28 23:03 ` Christoph Hellwig
2004-09-28 23:21 ` Dave Hansen
2004-09-29 14:46 ` Timur Tabi [this message]
2004-09-29 14:48 ` Timur Tabi
2004-09-29 15:01 ` Christoph Hellwig
2004-09-29 4:49 ` opening a file inside the kernel module Rakesh Jagota
2004-09-29 5:00 ` Jeff Garzik
2004-09-29 5:56 ` Rakesh Jagota
2004-09-29 15:52 ` Stuart MacDonald, linux-kernel-owner
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=415ACACE.1020008@ammasso.com \
--to=timur.tabi@ammasso.com \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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