Re: mmaping a kernel buffer to user space

Hi,

Jiri Slaby wrote:
Guillermo Marcus wrote:
Hi Jiri,

The fact that it does not works with RAM is well documented in LDD3,
pages 430++. It says (and I tested) that remap_xxx_range does not work
in this case. They suggest a method using nopage, similar to the one I
implement.

Could somebody confirm, that this still holds?

Apparently this restriction has been removed since 2.6.15 when
VM_PFNMAP flag has been introduced, see commit
6aab341e0a28aff100a09831c5300a2994b8b986

Why there's such restriction before 2.6.15, I haven't searched
yet, but any hints would be appreciated.

Thanks
Franck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: mmaping a kernel buffer to user space
    ... On 10/31/06, Jiri Slaby wrote: ... > The fact that it does not works with RAM is well documented in LDD3, ... can the limitation be removed, ...
    (Linux-Kernel)
  • Re: mmaping a kernel buffer to user space
    ... Guillermo Marcus wrote: ... The fact that it does not works with RAM is well documented in LDD3, ... They suggest a method using nopage, ...
    (Linux-Kernel)
  • Re: mmaping a kernel buffer to user space
    ... The fact that it does not works with RAM is well documented in LDD3, ... They suggest a method using nopage, ... To mmap ... pci_alloc_consistent as this memory is going to be used to perform DMA ...
    (Linux-Kernel)
  • Re: [PATCH 2.6.19-rc1 update4] drivers: add LCD support
    ... > remap RAM yourself with remap_pfn_range. ... MO> LDD3 states it must work like this. ... Also, my area was full of zeros, as LDD3 states. ... little further and I did what "Remapping RAM" explains. ...
    (Linux-Kernel)