From: Gregory Fong <firstname.lastname@example.org> To: Arnd Bergmann <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com>, Kevin Cernekee <firstname.lastname@example.org>, Russell King <email@example.com>, open list <firstname.lastname@example.org> Subject: Re: [PATCH 3/3] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build Date: Fri, 5 Jun 2015 12:27:49 -0700 [thread overview] Message-ID: <CADtm3G5LOzJRutVPnYyQe0+TiW3FM+e61voYo8AmqhQMYcwaemail@example.com> (raw) In-Reply-To: <2466892.NW5Y39MQOr@wuerfel> On Fri, Jun 5, 2015 at 5:26 AM, Arnd Bergmann <firstname.lastname@example.org> wrote: > On Thursday 04 June 2015 18:58:38 Gregory Fong wrote: >> ARMv7 chips with LPAE can often benefit from SPARSEMEM, as portions of >> system memory can be located deep in the 36-bit address space. Allow >> FLATMEM or SPARSEMEM to be selectable at compile time; FLATMEM remains >> the default. >> >> This is based on Kevin's "[PATCH 3/3] ARM: Allow either FLATMEM or >> SPARSEMEM on the multi-v7 build" from  and shamelessly rips off his >> commit message text above. As Arnd pointed out at  there doesn't >> seem to be any reason to tie this specifically to ARMv7, so this has >> been changed to apply to all multiplatform kernels. >> >>  http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286837.html >>  http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/298950.html >> >> Cc: Kevin Cernekee <email@example.com> >> Signed-off-by: Gregory Fong <firstname.lastname@example.org> >> --- >> I don't have any platforms other than armv7 handily set up to test SPARSEMEM, >> so any testing would be appreciated. FLATMEM is still the default so at least >> nobody will see anything change unless they deliberately switch. >> > > Can you check that realview at least builds with your series? It probably > will, but it's not obvious as there are some tricky bits with the > various realview config options. I just checked using realview_defconfig and realview-smp_defconfig, both built successfully. Best regards, Gregory
next prev parent reply other threads:[~2015-06-05 19:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-05 1:58 [PATCH 0/3] ARM: Allow SPARSEMEM on " Gregory Fong 2015-06-05 1:58 ` [PATCH 1/3] ARM: Add default SPARSEMEM settings Gregory Fong 2015-06-05 1:58 ` [PATCH 2/3] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting Gregory Fong 2015-06-05 12:23 ` Arnd Bergmann 2015-06-05 1:58 ` [PATCH 3/3] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build Gregory Fong 2015-06-05 12:26 ` Arnd Bergmann 2015-06-05 19:27 ` Gregory Fong [this message] 2015-06-16 23:08 ` [PATCH 0/3] ARM: Allow SPARSEMEM on " Gregory Fong 2015-06-17 19:00 ` Stephen Boyd
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='CADtm3G5LOzJRutVPnYyQe0+TiW3FM+e61voYo8AmqhQMYcwaemail@example.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH 3/3] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build' \ /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
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).