Reserving a fixed physical address page of RAM.
Quoted 30 lines · linux-os (Dick Johnson)
Quoted 6 lines · Jon Ringle
Quoted 5 lines · Robert Hancock
Quoted 4 lines · Jon Ringle
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.
Quoted 1 line
Quoted 1 line
Quoted 1 line
How can I ensure that the this area of RAM gets reseved
so that the
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Linux's memory management (
kmalloc()and friends) don't use it?Some things that I've considered are
iotable_init()andioremap(). However, I've seen these used for memory mapped IOdevices which are
Quoted 7 lines
Quoted 6 lines
Quoted 3 lines
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_coherentis what you want..It looks promising, however, I need to reserve a physical
address area
Quoted 4 lines
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_coherentreturns the address that it allocated. Instead I need something where I can tell it what physical addressand range I want to use.
Quoted 1 line
Quoted 8 lines
Quoted 1 line
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.
In my hardware setup, Linux is running in PCI option mode on a IXP455 processor and it exposes a segment of the IXP455's memory so that it is available on the PCI bus. The other processor (a pentium M running Windows OS) sees this exposed IXP455 memory as PCI memory from it's perspective.
Quoted 16 lines
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 useioremap()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 variablenum_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 thannum_physpages.
I'll take a look telling the kernel it has less memory that there physically exists and use ioremap() to map it in.
Thanks,
Jon