From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: akpm@linux-foundation.org
Cc: sunguoyun@loongson.cn, "Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Paul Burton" <paulburton@kernel.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Dmitry Korotin" <dkorotin@wavecomp.com>,
"Daniel Silsby" <dansilsby@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] mips/mm: Enable SOFT_DIRTY for all 64bit systems
Date: Mon, 27 Apr 2020 01:40:56 +0800 [thread overview]
Message-ID: <20200426174058.1181837-2-jiaxun.yang@flygoat.com> (raw)
In-Reply-To: <20200426174058.1181837-1-jiaxun.yang@flygoat.com>
64bit systems always have enough page table bits.
So we can safely enable it for all of them instead of for Loongson
only.
If oneday 32bit systems get 64bit PTEs than we can drop this
limition.
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
---
arch/mips/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 85011023839b..743ed9b9099e 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -45,6 +45,7 @@ config MIPS
select HAVE_ARCH_MMAP_RND_BITS if MMU
select HAVE_ARCH_MMAP_RND_COMPAT_BITS if MMU && COMPAT
select HAVE_ARCH_SECCOMP_FILTER
+ select HAVE_ARCH_SOFT_DIRTY if 64BIT
select HAVE_ARCH_TRACEHOOK
select HAVE_ARCH_TRANSPARENT_HUGEPAGE if CPU_SUPPORTS_HUGEPAGES
select HAVE_ASM_MODVERSIONS
@@ -495,7 +496,6 @@ config MACH_LOONGSON64
select COMMON_CLK
select USE_OF
select BUILTIN_DTB
- select HAVE_ARCH_SOFT_DIRTY
help
This enables the support of Loongson-2/3 family of machines.
--
2.26.0.rc2
next prev parent reply other threads:[~2020-04-26 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 17:40 [PATCH 1/2] mips/mm: Guard SOFT_DIRTY bit with config option Jiaxun Yang
2020-04-26 17:40 ` Jiaxun Yang [this message]
2020-04-27 8:55 ` [PATCH 2/2] mips/mm: Enable SOFT_DIRTY for all 64bit systems Sergei Shtylyov
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=20200426174058.1181837-2-jiaxun.yang@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=akpm@linux-foundation.org \
--cc=dansilsby@gmail.com \
--cc=dkorotin@wavecomp.com \
--cc=f4bug@amsat.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=sunguoyun@loongson.cn \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®