From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Cc: Jon Ringle <JRingle@vertical.com>
Subject: Re: Reserving a fixed physical address page of RAM.
Date: Mon, 27 Nov 2006 18:38:47 -0600 [thread overview]
Message-ID: <456B8517.7040502@shaw.ca> (raw)
In-Reply-To: <fa.LC2HgQx8572p2lwOKfUm6cxg95s@ifi.uio.no>
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..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-11-28 0:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.LC2HgQx8572p2lwOKfUm6cxg95s@ifi.uio.no>
2006-11-28 0:38 ` Robert Hancock [this message]
2006-11-28 3:36 ` Reserving a fixed physical address page of RAM Jon Ringle
2006-11-28 5:19 ` Robert Hancock
2006-11-28 5:34 ` Dave Airlie
2006-11-28 6:51 ` Fawad Lateef
2006-11-28 10:14 ` Jesper Juhl
2006-11-28 13:04 ` linux-os (Dick Johnson)
2006-11-30 21:51 Jon Ringle
-- strict thread matches above, loose matches on Subject: below --
2006-11-30 18:31 Jon Ringle
2006-11-30 18:56 ` Fawad Lateef
2006-11-30 17:47 Jon Ringle
2006-11-30 18:32 ` Fawad Lateef
2006-11-28 19:52 Jon Ringle
2006-11-28 19:37 Jon Ringle
2006-11-28 19:26 Jon Ringle
2006-11-27 16:31 Jon Ringle
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=456B8517.7040502@shaw.ca \
--to=hancockr@shaw.ca \
--cc=JRingle@vertical.com \
--cc=linux-kernel@vger.kernel.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