Hello Clemens, Konrad, others,
On Thu, May 19, 2011 at 5:58 PM, Clemens Ladisch <clemens@xxxxxxxxxx> wrote:
> Konrad Rzeszutek Wilk wrote:
>> On Thu, May 19, 2011 at 12:14:40AM +0200, Leon Woestenberg wrote:
>> > I cannot get my driver's mmap() to work. I allocate 64 KiB ringbuffer
>> > using pci_alloc_consistent(), then implement mmap() to allow programs
>> > to map that memory into their user space.
>> > ...
>> > int ringbuffer_vma_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
>> > {
>> > /* the buffer allocated with pci_alloc_consistent() */
>> > void *vaddr = ringbuffer_virt;
>> > int ret;
>> >
>> > /* find the struct page that describes vaddr, the buffer
>> > * allocated with pci_alloc_consistent() */
>> > struct page *page = virt_to_page(lro_char->engine->ringbuffer_virt);
>> > vmf->page = page;
>> >
>> > /*** I have verified that vaddr, page, and the pfn correspond with vaddr = pci_alloc_consistent() ***/
>> > ret = vm_insert_pfn(vma, address, page_to_pfn(page));
>>
>> address is the vmf->virtual_address?
>>
yes, I missed that line when removing some noise:
unsigned long address = (unsigned long)vmf->virtual_address;
>> And is the page_to_pfn(page) value correct? As in:
>>
>> int pfn = page_to_pfn(page);
>>
>> WARN(pfn << PAGE_SIZE != vaddr,"Something fishy.");
>>
Yes, this holds true.
I also verified that the pfn corresponds with the pfn of the virtual
address returned by pci_alloc_consistent().
>> Hm, I think I might have misled you now that I look at that WARN.
>>
>> The pfn to be supplied has to be physical page frame number. Which in
>> this case should be your bus addr shifted by PAGE_SIZE. Duh! Try that
>> value.
>
The physical address? Why? (Just learning here, this is no objection
to your suggestion.)
Also, the bus address is not the physical address, or not in general.
For example on IOMMU systems this certainly doesn't hold true.
So how can I reliably find the out the physical memory address of
pci_alloc_consistent() memory?
> There are wildly different implementations of pci_alloc_consistent
> (actually dma_alloc_coherent) that can return somewhat different
> virtual and/or physical addresses.
>
>> I think a better example might be the 'hpet_mmap' code
>
> Which is x86 and ia64 only.
>
>> > static int ringbuffer_mmap(struct file *file, struct vm_area_struct *vma)
>> > {
>> > vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
>
> So is this an architecture without coherent caches?
>
My aim is to have an architecture independent driver.
My goal is to make sure the CPU can poll for data that the PCI(e) bus
master writes into host memory.
> Or would you want to use pgprot_dmacoherent, if available?
>
Hmm, let me check that.
> I recently looked into this problem, and ended up with the code below.
> I then decided that streaming DMA mappings might be a better idea.
>
I got streaming DMA mappings working already. I cannot use them in my
case as streaming mappings are not cache-coherent in general.
Thanks for the code snippet, it seems x86 only though?
Regards,
--
Leon
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx 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