From: "Fawad Lateef" <fawadlateef@gmail.com>
To: "Jon Ringle" <JRingle@vertical.com>
Cc: "Dave Airlie" <airlied@gmail.com>,
"Robert Hancock" <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org
Subject: Re: Reserving a fixed physical address page of RAM.
Date: Thu, 30 Nov 2006 23:32:14 +0500 [thread overview]
Message-ID: <1e62d1370611301032q9cfd2f0jbbe5e249fb114530@mail.gmail.com> (raw)
In-Reply-To: <22170ADB26112F478A4E293FF9D449F44D105B@secure.comdial.com>
On 11/30/06, Jon Ringle <JRingle@vertical.com> wrote:
> Fawad Lateef wrote:
> > On 11/30/06, Jon Ringle <JRingle@vertical.com> wrote:
> > > Fawad Lateef wrote:
> > > > 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.
> > >
> > > Seems that using mem= has to be in 1MB increments, where I
> > only need 4K.
> > >
> >
> > No AFAIK you can specify it in KBs (see
> > http://sosdg.org/~coywolf/lxr/source/Documentation/kernel-para
> > meters.txt#L869)
>
> Yes, you can specify the mem= using K notation, but there is a test in
> arch/arm/mm/mm-armv.c:create_mapping() that prevents the mapping from
> being created if the boundaries are not MB aligned:
>
> if (mem_types[md->type].prot_l1 == 0 &&
> (virt & 0xfffff || (virt + off) & 0xfffff || (virt + length)
> & 0xfffff)) {
> printk(KERN_WARNING "BUG: map for 0x%08lx at 0x%08lx can
> not "
> "be mapped using pages, ignoring.\n",
> __pfn_to_phys(md->pfn), md->virtual);
> return;
> }
>
> This is in linux-2.6.16.29.
>
Ohh ok, I don't know about this architecture related information.
> >
> > > >
> > > > 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).
> > >
> > > Do you think that the following would work to properly reserve the
> > > memory. If it does, then I think I can just do a ioremap(0x0ffff000,
> > > 0x1000) to obtain a virtual address. (Ofcourse I would actually use
> > > symbolic names rather than the hardcoded addesses shown here).
> > >
> > > Index: linux/arch/arm/mm/init.c
> > > ===================================================================
> > > --- linux.orig/arch/arm/mm/init.c 2006-11-30
> > 11:03:00.000000000
> > > -0500
> > > +++ linux/arch/arm/mm/init.c 2006-11-30 11:09:09.000000000 -0500
> > > @@ -429,6 +429,10 @@
> > > unsigned long addr;
> > > void *vectors;
> > >
> > > +#ifdef CONFIG_MACH_VERTICAL_RSC4
> > > + reserve_bootmem (0x0ffff000, 0x1000); #endif
> > > +
> > > /*
> > > * Allocate the vector page early.
> > > */
> > >
> > >
> >
> > I think you can do like this but can't say accurately because
> > I havn't worked on arm architecture and also you havn't
> > mentioned your kernel-version or function (in file
> > arch/arm/mm/init.c) which you are going to do call reserve_bootmem !
>
> Kernel version is 2.6.16.29 and the reserve_bootmem() call above is at
> the top of the function devicemaps_init().
>
reserving_bootmem in devicemaps_init will work but I think it will be
better if you do this in mem_init function (here:
http://sosdg.org/~coywolf/lxr/source/arch/arm/mm/init.c?v=2.6.16;a=arm#L620),
so that all the paging and other map related stuff completes. (CMIIW)
--
Fawad Lateef
next prev parent reply other threads:[~2006-11-30 18:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 17:47 Reserving a fixed physical address page of RAM Jon Ringle
2006-11-30 18:32 ` Fawad Lateef [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-30 21:51 Jon Ringle
2006-11-30 18:31 Jon Ringle
2006-11-30 18:56 ` Fawad Lateef
2006-11-28 19:52 Jon Ringle
2006-11-28 19:37 Jon Ringle
2006-11-28 19:26 Jon Ringle
[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
2006-11-28 13:04 ` linux-os (Dick Johnson)
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=1e62d1370611301032q9cfd2f0jbbe5e249fb114530@mail.gmail.com \
--to=fawadlateef@gmail.com \
--cc=JRingle@vertical.com \
--cc=airlied@gmail.com \
--cc=hancockr@shaw.ca \
--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