From: Ben Hutchings <ben@decadent.org.uk>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Michael Ellerman <patch-notifications@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: powerpc/mm: Only define MAX_PHYSMEM_BITS in SPARSEMEM configurations
Date: Mon, 25 Mar 2019 03:54:18 +0000 [thread overview]
Message-ID: <cf9154f1812e0e9a328a1e21ef13d80a46e5feb6.camel@decadent.org.uk> (raw)
In-Reply-To: <87ftrbq0qe.fsf@igel.home>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Mon, 2019-03-25 at 01:03 +0100, Andreas Schwab wrote:
> On Mär 24 2019, Ben Hutchings <ben@decadent.org.uk> wrote:
>
> > Presumably you have CONFIG_PPC_BOOK3S_64 enabled and
> > CONFIG_SPARSEMEM
> > disabled? Was this configuration actually usable?
>
> Why not?
I assume that CONFIG_SPARSEMEM is the default for a good reason.
What I don't know is how strong that reason is (I am not a Power expert
at all). Looking a bit further, it seems to be related to CONFIG_NUMA
in that you can enable CONFIG_FLATMEM if and only if that's disabled.
So I suppose the configuration you used works for non-NUMA systems.
Anyway, does the patch I sent work for you?
Ben.
--
Ben Hutchings
I'm not a reverse psychological virus.
Please don't copy me into your signature.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-25 3:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 1:17 [PATCH] powerpc/mm: Only define MAX_PHYSMEM_BITS in SPARSEMEM configurations Ben Hutchings
2019-03-22 12:21 ` Michael Ellerman
[not found] ` <44QjSh4zGhz9sV2__48832.6491251186$1553257542$gmane$org@ozlabs.org>
2019-03-24 22:18 ` Andreas Schwab
2019-03-24 23:05 ` Ben Hutchings
2019-03-25 0:03 ` Andreas Schwab
2019-03-25 3:54 ` Ben Hutchings [this message]
2019-03-25 11:35 ` Michael Ellerman
2019-03-25 12:03 ` Christophe Leroy
2019-03-25 20:12 ` Andreas Schwab
2019-04-02 12:57 ` Aneesh Kumar K.V
2019-03-25 8:54 Rui Salvaterra
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=cf9154f1812e0e9a328a1e21ef13d80a46e5feb6.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=patch-notifications@ellerman.id.au \
--cc=paulus@samba.org \
--cc=schwab@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).