From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/nohash: Split __early_init_mmu() into boot and secondary
Date: Thu, 07 Aug 2014 06:46:07 +1000 [thread overview]
Message-ID: <1407357967.3073.103.camel@pasglop> (raw)
In-Reply-To: <1407355754.7427.36.camel@snotra.buserror.net>
On Wed, 2014-08-06 at 15:09 -0500, Scott Wood wrote:
> BTW, is there a particular reason why we need to use
> memblock_enforce_memory_limit() on FSL_BOOK3E, rather than relying on
> memblock_set_current_limit()? I see that when
> memblock_enforce_memory_limit() was added to __early_init_mmu(),
> memblock_set_current_limit() did not exist. On 32-bit fsl booke uses
> memblock_set_current_limit() for this.
I don't remember. I don't even know what the difference is, I can
have a look later if you want but I'd rather you did :-)
Cheers,
Ben.
prev parent reply other threads:[~2014-08-06 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 3:07 [PATCH 1/2] powerpc/64e: Add __ref to early_alloc_pgtable() Scott Wood
2014-08-02 3:07 ` [PATCH 2/2] powerpc/nohash: Split __early_init_mmu() into boot and secondary Scott Wood
2014-08-05 4:36 ` Benjamin Herrenschmidt
2014-08-06 0:48 ` Scott Wood
2014-08-06 4:58 ` Benjamin Herrenschmidt
2014-08-06 20:09 ` Scott Wood
2014-08-06 20:46 ` Benjamin Herrenschmidt [this message]
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=1407357967.3073.103.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).