From: Leon Woestenberg <leon.woestenberg@gmail.com>
To: linux-pci@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-mm@kvack.org
Subject: Re: driver mmap implementation for memory allocated with pci_alloc_consistent()?
Date: Wed, 18 May 2011 17:03:41 +0200 [thread overview]
Message-ID: <BANLkTikxzEb7UkUfxmdHhHMc04P4bmKGXQ@mail.gmail.com> (raw)
In-Reply-To: <20110518144129.GB4296@dumpdata.com>
Hello,
On Wed, May 18, 2011 at 4:41 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Wed, May 18, 2011 at 03:02:30PM +0200, Leon Woestenberg wrote:
>>
>> memory allocated with pci_alloc_consistent() returns the (kernel)
>> virtual address and the bus address (which may be different from the
>> physical memory address).
>>
>> What is the correct implementation of the driver mmap (file operation
>> method) for such memory?
>
> You are going to use the physical address from the CPU side. So not
> the bus address. Instead use the virtual address and find the
> physical address from that. page_to_pfn() does a good job.
>
pci_alloc_consistent() returns a kernel virtual address. To find the
page I think virt_to_page() suits me better, right?
#define virt_to_page(kaddr) pfn_to_page(__pa(kaddr) >> PAGE_SHIFT)
> Then you can call 'vm_insert_page(vma...)'
>
> Or 'vm_insert_mixed'
Thanks, that opens a whole new learning curve experience.
Can I call vmalloc_to_page() on memory allocated with
pci_alloc_consistent()? If so, then remap_vmalloc_range() looks
promising.
I could not find PCI driver examples calling vm_insert_page() and I am
know I can trip into the different memory type pointers easily.
How does your suggestion relate to using the vma ops fault() (formerly
known as nopage() to mmap memory allocated by pci_alloc_consistent()?
i.e. Such as suggested in
http://www.gossamer-threads.com/lists/linux/kernel/702127#702127
> Use 'cscope' on the Linux kernel.
Thanks for the suggestion. How would cscope help me find
vm_insert_page() given my question?
On hind-sight all questions seem to be easy once finding the correct
Documentation / source-code in the first place. I usually use
http://lxr.linux.no/ and friends.
Regards,
--
Leon
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2011-05-18 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTimo=yXTrgjQHn9746oNdj97Fb-Y9Q@mail.gmail.com>
[not found] ` <20110518144129.GB4296@dumpdata.com>
2011-05-18 15:03 ` Leon Woestenberg [this message]
2011-05-18 15:40 ` driver mmap implementation for memory allocated with pci_alloc_consistent()? Konrad Rzeszutek Wilk
2011-05-18 19:35 ` Leon Woestenberg
2011-05-18 22:59 ` Leon Woestenberg
[not found] ` <1305767957.2375.117.camel@sli10-conroe>
2011-05-19 1:34 ` Leon Woestenberg
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=BANLkTikxzEb7UkUfxmdHhHMc04P4bmKGXQ@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.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).