From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: Add default SPARSEMEM settings
Date: Fri, 31 Oct 2014 21:47:55 +0100 [thread overview]
Message-ID: <3450236.7ui9jXEKqb@wuerfel> (raw)
In-Reply-To: <CADtm3G6vygCo8LK5drqCNH6r3gp8kPq6BrnMFjxJ2Q=BX7YKmg@mail.gmail.com>
On Friday 31 October 2014 13:11:54 Gregory Fong wrote:
> On Thu, Sep 11, 2014 at 7:22 PM, Kevin Cernekee <cernekee@gmail.com> wrote:
> > We can still override these settings via mach/memory.h, but let's provide
> > sensible defaults so that SPARSEMEM is available in the multiplatform
> > kernels.
> >
> > Two platforms currently use SECTION_SIZE_BITS < 28, but are expected to
> > work with 28 (albeit slightly less efficiently if not all banks are
> > populated):
> >
> > - mach-rpc: uses 26 bits. Based on mach/hardware.h it looks like this
> > platform puts RAM at 0x1000_0000 - 0x1fff_ffff, and I/O below
> > 0x1000_0000.
> >
> > - mach-sa1100: uses 27 bits. mach/memory.h indicates that RAM occupies
> > the entire range of 0xc000_0000 - 0xdfff_ffff.
> >
> > Several platforms need MAX_PHYSMEM_BITS >= 36 so we'll pick that as the
> > minimum. Anything higher and we'll fail the SECTIONS_WIDTH + NODES_WIDTH +
> > ZONES_WIDTH test in <linux/mm.h>.
> >
> > Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
>
> Acked-by: Gregory Fong <gregory.0xf0@gmail.com>
>
I didn't see this patch originally, just saw the reply. The patch looks
good, but it's worth noting in the changelog that rpc and sa1100 will
never have to use the default, because they cannot be part of a multiplatform
kernel, and that is very unlikely to ever change.
Acked-by: Arnd Bergmann <arnd@arndb.de>
Arnd
next prev parent reply other threads:[~2014-10-31 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 2:22 [PATCH 1/3] ARM: Add default SPARSEMEM settings Kevin Cernekee
2014-09-12 2:22 ` [PATCH 2/3] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting Kevin Cernekee
2014-10-31 20:12 ` Gregory Fong
2014-09-12 2:22 ` [PATCH 3/3] ARM: Allow either FLATMEM or SPARSEMEM on the multi-v7 build Kevin Cernekee
2014-10-31 20:12 ` Gregory Fong
2014-10-31 20:48 ` Arnd Bergmann
2014-10-31 20:11 ` [PATCH 1/3] ARM: Add default SPARSEMEM settings Gregory Fong
2014-10-31 20:47 ` Arnd Bergmann [this message]
2014-10-31 21:00 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2015-06-05 1:58 [PATCH 0/3] ARM: Allow SPARSEMEM on multiplatform build Gregory Fong
2015-06-05 1:58 ` [PATCH 1/3] ARM: Add default SPARSEMEM settings Gregory Fong
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=3450236.7ui9jXEKqb@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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