mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Fawad Lateef" <fawadlateef@gmail.com>
Cc: "Dave Airlie" <airlied@gmail.com>,
	"Jon Ringle" <jringle@vertical.com>,
	"Robert Hancock" <hancockr@shaw.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: Reserving a fixed physical address page of RAM.
Date: Tue, 28 Nov 2006 11:14:44 +0100	[thread overview]
Message-ID: <9a8748490611280214s711d4f6eq6100a574af22f8a7@mail.gmail.com> (raw)
In-Reply-To: <1e62d1370611272251r6cb797el26bc4f96e0958092@mail.gmail.com>

On 28/11/06, Fawad Lateef <fawadlateef@gmail.com> wrote:
> On 11/28/06, Dave Airlie <airlied@gmail.com> wrote:
> > On 11/28/06, Jon Ringle <jringle@vertical.com> wrote:
> <snip>
> > > 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.
> > >
> >
> > I've seen other projects just boot a 128M board with mem=120M and just
> > use the 8MB at 120 to talk to the other processor..
> >
>
> Yes, this can be used if required physical-memory exists in the last
> part of RAM as if you use mem=<xxxM> then kernel will only use memory
> less than or equal-to <xxxM> and above can be used by drivers (or any
> kernel module) might be through ioremap which takes physical-address.
>
> But if lets say we need only 1MB portion of specific physical-memory
> region then AFAIK it must be done by hacking in kernel code during
> memory-initialization (mem_init function) where it is marking/checking
> pages as/are reserved; you can simply mark you required pages as
> reserved too and set their count to some-value if you want to know
> later which pages are reserved by you. (can do this reservation work
> here: http://lxr.free-electrons.com/source/arch/i386/mm/init.c#605).
> CMIIW
>

Can you not use the 'memmap=' kernel option to reserve the specific
area you need?
(See Documentation/kernel-parameters.txt for details)

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-11-28 10:14 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
2006-11-28  3:36   ` 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 [this message]
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=9a8748490611280214s711d4f6eq6100a574af22f8a7@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=airlied@gmail.com \
    --cc=fawadlateef@gmail.com \
    --cc=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

all inboxes | Powered by JetHome®