linux-mips
[Top] [All Lists]

Re: Boot time memory allocation

To: Alex Gonzalez <langabe@gmail.com>
Subject: Re: Boot time memory allocation
From: Ralf Baechle <ralf@linux-mips.org>
Date: Tue, 9 May 2006 17:34:11 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <c58a7a270605090735t8e4f21ax6ca87f97b9143e3b@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <c58a7a270605090735t8e4f21ax6ca87f97b9143e3b@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.2.1i
On Tue, May 09, 2006 at 03:35:14PM +0100, Alex Gonzalez wrote:

> I have two independent processors with access to a shared memory
> region, mapped in the 256MB to 512MB region (kseg0).
> 
> One is running a propietary OS, and the second one is running Linux 2.6.12.
> 
> How would I arrange to leave that shared memory region out of the
> scope of Linux's memory management system, but at the same time make
> it possible for a driver to access it?
> 
> I have done similar things before with the help of alloc_bootmem, but
> this time I don't want the kernel to reserve the memory, I want the
> kernel to be completely unaware of it, and I need to specify its start
> and end.

At kernel initialization time just don't tell the kernel about the
existence of your memory region.  For many systems that just means you
shrink the memory region passed to the add_memory_region() call to
something that suits your platform.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>