From: "Mark.Zhan" <rongkai.zhan@windriver.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Alex Gonzalez <langabe@gmail.com>, linux-mips@linux-mips.org
Subject: Re: Boot time memory allocation
Date: Wed, 10 May 2006 10:21:03 +0800 [thread overview]
Message-ID: <44614E0F.2000207@windriver.com> (raw)
In-Reply-To: <20060509163411.GA8528@linux-mips.org>
Ralf Baechle wrote:
> 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
>
Maybe it is a more flexible way to specify the memory regions via
command line. You know, this will produce User-defined memory regions to
kernel.
next prev parent reply other threads:[~2006-05-10 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 14:35 Boot time memory allocation Alex Gonzalez
2006-05-09 16:34 ` Ralf Baechle
2006-05-10 2:21 ` Mark.Zhan [this message]
2006-05-10 9:11 ` Alex Gonzalez
2006-05-12 0:41 ` SOAP Ratin
2006-05-12 0:41 ` SOAP Ratin
2006-05-12 7:08 ` SOAP Leon Zhang
2006-05-12 7:50 ` SOAP Ralf Roesch
2006-05-10 15:35 ` Boot time memory allocation Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44614E0F.2000207@windriver.com \
--to=rongkai.zhan@windriver.com \
--cc=langabe@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox