From: Ankita Garg <ankita@in.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-mm@kvack.org
Subject: Re: Reserved pages in PowerPC
Date: Tue, 28 Sep 2010 15:58:51 +0530 [thread overview]
Message-ID: <20100928102851.GF1990@in.ibm.com> (raw)
In-Reply-To: <1284673951.30449.93.camel@pasglop>
Hi Ben,
On Fri, Sep 17, 2010 at 07:52:31AM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2010-09-16 at 17:38 +0530, Ankita Garg wrote:
> > Thanks Ben for taking a look at this. So I checked the rtas messages
> > on
> > the serial console and see the following:
> >
> > instantiating rtas at 0x000000000f632000... done
> >
> > Which does not correspond to the higher addresses that I see as
> > reserved
> > (observation on a 16G machine).
>
> Well, I'd suggest you audit prom_init.c which builds the reserve map,
> and the various memblock_reserve() calls in prom.c
>
I studied and instrumented memblock_reserve() and also reserve_mem().
However, all the reserved addresses seem to correspond to lower memory.
I also observed that these reserved addresses are accessed quite rapidly
when a workload is being run..
--
Regards,
Ankita Garg (ankita@in.ibm.com)
Linux Technology Center
IBM India Systems & Technology Labs,
Bangalore, India
WARNING: multiple messages have this Message-ID (diff)
From: Ankita Garg <ankita@in.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-mm@kvack.org
Subject: Re: Reserved pages in PowerPC
Date: Tue, 28 Sep 2010 15:58:51 +0530 [thread overview]
Message-ID: <20100928102851.GF1990@in.ibm.com> (raw)
In-Reply-To: <1284673951.30449.93.camel@pasglop>
Hi Ben,
On Fri, Sep 17, 2010 at 07:52:31AM +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2010-09-16 at 17:38 +0530, Ankita Garg wrote:
> > Thanks Ben for taking a look at this. So I checked the rtas messages
> > on
> > the serial console and see the following:
> >
> > instantiating rtas at 0x000000000f632000... done
> >
> > Which does not correspond to the higher addresses that I see as
> > reserved
> > (observation on a 16G machine).
>
> Well, I'd suggest you audit prom_init.c which builds the reserve map,
> and the various memblock_reserve() calls in prom.c
>
I studied and instrumented memblock_reserve() and also reserve_mem().
However, all the reserved addresses seem to correspond to lower memory.
I also observed that these reserved addresses are accessed quite rapidly
when a workload is being run..
--
Regards,
Ankita Garg (ankita@in.ibm.com)
Linux Technology Center
IBM India Systems & Technology Labs,
Bangalore, India
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-09-28 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 5:23 Reserved pages in PowerPC Ankita Garg
2010-09-16 5:23 ` Ankita Garg
2010-09-16 10:04 ` Benjamin Herrenschmidt
2010-09-16 10:04 ` Benjamin Herrenschmidt
2010-09-16 12:08 ` Ankita Garg
2010-09-16 12:08 ` Ankita Garg
2010-09-16 21:52 ` Benjamin Herrenschmidt
2010-09-16 21:52 ` Benjamin Herrenschmidt
2010-09-28 10:28 ` Ankita Garg [this message]
2010-09-28 10:28 ` Ankita Garg
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=20100928102851.GF1990@in.ibm.com \
--to=ankita@in.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.