From: Joshua Kinard <kumba@gentoo.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: [PATCH]: R10000: Mark CPU_SUPPORTS_HUGEPAGES as broken
Date: Mon, 10 Nov 2014 01:46:26 -0500 [thread overview]
Message-ID: <54605F42.1040403@gentoo.org> (raw)
Enabling CONFIG_TRANSPARENT_HUGEPAGE on an R10000-family processor on at least
SGI IP27 and IP30 machines creates problems, including random SIGSEGV and
SIGBUS signals to processes that attempt to use huge pages. Until someone with
deeper TLB knowledge on R10K can attempt to solve this problem, marking
CPU_SUPPORTS_HUGEPAGES as BROKEN seems like a sensible thing to do.
Signed-off-by: Joshua Kinard <kumba@gentoo.org>
---
arch/mips/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 5c3992c..7432be6 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -1418,7 +1418,7 @@ config CPU_R10000
select CPU_SUPPORTS_32BIT_KERNEL
select CPU_SUPPORTS_64BIT_KERNEL
select CPU_SUPPORTS_HIGHMEM
- select CPU_SUPPORTS_HUGEPAGES
+ select CPU_SUPPORTS_HUGEPAGES if BROKEN
help
MIPS Technologies R10000-series processors.
reply other threads:[~2014-11-10 6:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54605F42.1040403@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.