From: Paul Mackerras <paulus@ozlabs.org>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH RFC 2/3] powerpc/64: Always enable radix support for 64-bit Book 3S kernels
Date: Mon, 5 Dec 2016 19:03:39 +1100 [thread overview]
Message-ID: <20161205080339.GB13528@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <20161205080219.GA13528@fergus.ozlabs.ibm.com>
This removes the ability for the user to choose whether or not to
include support for the radix MMU in kernels built to run on 64-bit
Book 3S machines. Excluding radix support saves only about 25kiB
of text and 13kiB of data, a total of little over half a page.
Having the option expands the space of option combinations that
need to be tested, which is an ongoing burden on developers,
as well as increasing the number of #ifdefs in the code.
Given that the space savings are small, let's remove the option.
Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
---
arch/powerpc/platforms/Kconfig.cputype | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/arch/powerpc/platforms/Kconfig.cputype b/arch/powerpc/platforms/Kconfig.cputype
index ca2da30..52a71ca 100644
--- a/arch/powerpc/platforms/Kconfig.cputype
+++ b/arch/powerpc/platforms/Kconfig.cputype
@@ -333,13 +333,8 @@ config PPC_STD_MMU_64
depends on PPC_STD_MMU && PPC64
config PPC_RADIX_MMU
- bool "Radix MMU Support"
+ def_bool y
depends on PPC_BOOK3S_64
- default y
- help
- Enable support for the Power ISA 3.0 Radix style MMU. Currently this
- is only implemented by IBM Power9 CPUs, if you don't have one of them
- you can probably disable this.
config PPC_MMU_NOHASH
def_bool y
--
2.7.4
next prev parent reply other threads:[~2016-12-05 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 8:02 [PATCH 1/3] powerpc/64: Fixes for the ibm,client-architecture-support options Paul Mackerras
2016-12-05 8:03 ` Paul Mackerras [this message]
2016-12-05 8:04 ` [PATCH RFC 3/3] powerpc/64: Enable use of radix MMU under hypervisor on POWER9 Paul Mackerras
2016-12-05 8:55 ` Benjamin Herrenschmidt
2016-12-05 9:47 ` Paul Mackerras
2016-12-06 3:45 ` [PATCH RFC v2 " Paul Mackerras
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=20161205080339.GB13528@fergus.ozlabs.ibm.com \
--to=paulus@ozlabs.org \
--cc=linuxppc-dev@ozlabs.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).