From: Nick Piggin <nickpiggin@yahoo.com.au>
To: markh@compro.net
Cc: dmarkh@cfl.rr.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: get_user_pages ?
Date: Sat, 22 Apr 2006 14:09:29 +1000 [thread overview]
Message-ID: <4449AC79.2010509@yahoo.com.au> (raw)
In-Reply-To: <4448D047.8070202@compro.net>
Mark Hounschell wrote:
>>OK, I'd suggest either using vm_insert_page, or converting it all over
>>to a ->nopage handler then.
>>
>
>
> I set the bit back on after get_user_pages and now I seem to be OK.
>
> You've looked at the code some obviously. What is in my future WRT these
> changes being made that you referenced above and the depreciation of
> some of the calls in use. Given my situation, do you foresee anything
> that will keep me from being able to get valid bus addresses for my pte?
Well remap_pfn_range / io_remap_pfn_range is a good option, but it
shouldn't really support get_user_pages so I suspect you are just
lucky there (ie. on some platforms you might not have a struct page
for your bus address, and other times the final put_page will try
to free the page).
If you definitely have struct pages, vm_insert_page is an option,
unless the memory is allocated with dma_alloc_* or similar, in
which case you should probably be using remap_pfn_range.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
prev parent reply other threads:[~2006-04-22 19:57 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
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 [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=4449AC79.2010509@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=dmarkh@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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.