On Mon, 27 Nov 2006, Jon Ringle wrote:
> Robert Hancock wrote:
>> Jon Ringle wrote:
>>> Hi,
>>>
>>> I need to reserve a page of memory at a specific area of RAM that will
>>> be used as a "shared memory" with another processor over PCI. How can I
>>> ensure that the this area of RAM gets reseved so that the Linux's memory
>>> management (kmalloc() and friends) don't use it?
>>>
>>> Some things that I've considered are iotable_init() and ioremap().
>>> However, I've seen these used for memory mapped IO devices which are
>>> outside of the RAM memory. Can I use them for reseving RAM too?
>>>
>>> I appreciate any advice in this regard.
>>
>> Sounds to me like dma_alloc_coherent is what you want..
>>
> It looks promising, however, I need to reserve a physical address area
> that is well known (so that the code running on the other processor
> knows where in PCI memory to write to). It appears that
> dma_alloc_coherent returns the address that it allocated. Instead I need
> something where I can tell it what physical address and range I want to use.
>
> Jon
First, "PCI memory" is some memory inside a board that is addressed through the
PCI bus. This address is allocated upon machine start and is available though
the PCI interface (check any of the PCI card drivers). If you want to access
this memory, you need to follow the same procedures that other boards use.
However, perhaps you don't mean "PCI memory". Perhaps you mean real memory
in the address-space, and you need to reserve it and give its physical address
to something inside a PCI-bus card, perhaps for DMA. In that case, you can
either memory-map some physical memory (get_dma_pages()) or you can tell the
kernel you have less memory than you really have, and use the memory the kernel
doesn't know about for your own private purposes. To access this private memory
you use ioremap() and friends. This can be memory-mapped to user-space as well
so you can perform DMA directly to user-space buffers. You can find the highest
address that the kernel uses by reading kernel variable num_physpages. This
tells the number of pages the kernel uses. The kernel does write to the next one
so you need to start using pages that are two higher than num_physpages.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.72 BogoMips).
New book: http://www.AbominableFirebug.com/
_
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
