From: Mark Hounschell <markh@compro.net>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: dmarkh@cfl.rr.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: get_user_pages ?
Date: Thu, 20 Apr 2006 15:53:40 -0400 [thread overview]
Message-ID: <4447E6C4.9070207@compro.net> (raw)
In-Reply-To: <44477585.4030508@yahoo.com.au>
Nick Piggin wrote:
> Mark Hounschell wrote:
>> For some reason (unknown to me) the VM_IO and even newer VM_PFNMAP
>> vm_flags are set when I use this call causing it to fail for me. I'm
>> currently using 2.6.16.9 on an x86 platform.
>
> [...]
>
>> I'm not the author of any of this code so please gentle with me. Nor do
>> I have much of an understanding of the vm system. Any help in how this
>> task should really be accomplished, taken the stated limitations of the
>> pci card in mind, would be greatly appreciated. And any help as to what
>> would just make it work again would also be greatly appreciated. As I
>> stated above this all worked fine until the VM_PFNMAP bit was added to
>> the vm->flags and subsequently checked for in the get_user_pages call.
>
> remap_pfn_range isn't the best API for someone who needs get_user_pages.
> remap_pfn_range operates on the pfn level only, so underlying addresses
> may not even have a struct page.
>
> This area is going through some changes lately. If you want something to
> quickly get things working, removing VM_PFNMAP from your vma flags should
> work.
>
Yes, that actually does work while the task is running but as soon as I
exit the task the machine freezes.
Mark
next prev parent reply other threads:[~2006-04-20 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 10:08 get_user_pages ? Mark Hounschell
2006-04-20 11:50 ` Nick Piggin
2006-04-20 19:53 ` Mark Hounschell [this message]
2006-04-20 20:00 ` Nick Piggin
2006-04-21 12:29 ` Mark Hounschell
2006-04-21 14:52 ` Mark Rustad
2006-04-22 4:09 ` Nick Piggin
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=4447E6C4.9070207@compro.net \
--to=markh@compro.net \
--cc=dmarkh@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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).