From: Andy Whitcroft <apw@shadowen.org>
To: Anton Blanchard <anton@au1.ibm.com>, Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: PPC32 memory models
Date: Mon, 28 Nov 2005 19:06:11 +0000 [thread overview]
Message-ID: <438B5523.40903@shadowen.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
It seems that there is some confusion over what we should be supporting
memory model wise for PPC32 under powerpc architecture. The current
Kconfig limits you to only SPARSEMEM which isn't parameterised for PPC32
at all. Are we expecting to be able to support PPC32 as yet in this
architecture? If so it seems we have a couple of issues with the Kconfig.
Attached is a patch to enable FLATMEM and disable SPARSEMEM for PPC32
which seems to be the working combinations. It may well not be what is
intended. But I offer it to start discussions.
Comments.
-apw
[-- Attachment #2: sparsemem-powerpc-allow-flatmem-on-32bit --]
[-- Type: text/plain, Size: 796 bytes --]
powerpc: ppc32 clean up available memory models
Clean up the currently available memory models for ppc32. It seems
that we do need FLATMEM for ppc32 on non-NUMA. It also seems that
SPARSEMEM is not parameterised yet so disable that.
Signed-off-by: Andy Whitcroft <apw@shadwen.org>
---
diff -upN reference/arch/powerpc/Kconfig current/arch/powerpc/Kconfig
--- reference/arch/powerpc/Kconfig
+++ current/arch/powerpc/Kconfig
@@ -584,14 +584,15 @@ config ARCH_SELECT_MEMORY_MODEL
config ARCH_FLATMEM_ENABLE
def_bool y
- depends on PPC64 && !NUMA
+ depends on !NUMA
config ARCH_SPARSEMEM_ENABLE
def_bool y
+ depends on PPC64
config ARCH_SPARSEMEM_DEFAULT
def_bool y
- depends on SMP && PPC_PSERIES
+ depends on SMP && PPC_PSERIES && NUMA
source "mm/Kconfig"
next reply other threads:[~2005-11-28 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 19:06 Andy Whitcroft [this message]
2005-11-29 1:58 ` PPC32 memory models Paul Mackerras
2005-11-29 19:20 ` [PATCH] powerpc ppc32 clean up available " Andy Whitcroft
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=438B5523.40903@shadowen.org \
--to=apw@shadowen.org \
--cc=anton@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.