From: Mike Rapoport <rppt@kernel•org>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Alexander Viro <viro@zeniv•linux.org.uk>,
Andy Lutomirski <luto@kernel•org>, Arnd Bergmann <arnd@arndb•de>,
Borislav Petkov <bp@alien8•de>,
Catalin Marinas <catalin.marinas@arm•com>,
Christopher Lameter <cl@linux•com>,
Dan Williams <dan.j.williams@intel•com>,
Dave Hansen <dave.hansen@linux•intel.com>,
David Hildenbrand <david@redhat•com>,
Elena Reshetova <elena.reshetova@intel•com>,
"H. Peter Anvin" <hpa@zytor•com>,
Hagen Paul Pfeifer <hagen@jauu•net>,
Ingo Molnar <mingo@redhat•com>,
James Bottomley <James.Bottomley@HansenPartnership•com>,
James Bottomley <jejb@linux•ibm.com>,
Kees Cook <keescook@chromium•org>,
"Kirill A. Shutemov" <kirill@shutemov•name>,
Matthew Wilcox <willy@infradead•org>,
Matthew Garrett <mjg59@srcf•ucam.org>,
Mark Rutland <mark.rutland@arm•com>,
Michal Hocko <mhocko@suse•com>,
Mike Rapoport <rppt@linux•ibm.com>,
Mike Rapoport <rppt@kernel•org>,
Michael Kerrisk <mtk.manpages@gmail•com>,
Palmer Dabbelt <palmer@dabbelt•com>,
Palmer Dabbelt <palmerdabbelt@google•com>,
Paul Walmsley <paul.walmsley@sifive•com>,
Peter Zijlstra <peterz@infradead•org>,
"Rafael J. Wysocki" <rjw@rjwysocki•net>,
Rick Edgecombe <rick.p.edgecombe@intel•com>,
Roman Gushchin <guro@fb•com>, Shakeel Butt <shakeelb@google•com>,
Shuah Khan <shuah@kernel•org>,
Thomas Gleixner <tglx@linutronix•de>,
Tycho Andersen <tycho@tycho•ws>, Will Deacon <will@kernel•org>,
Yury Norov <yury.norov@gmail•com>,
linux-api@vger•kernel.org, linux-arch@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-fsdevel@vger•kernel.org, linux-mm@kvack•org,
linux-kernel@vger•kernel.org, linux-kselftest@vger•kernel.org,
linux-nvdimm@lists•01.org, linux-riscv@lists•infradead.org,
x86@kernel•org, kernel test robot <lkp@intel•com>
Subject: [PATCH v20 2/7] riscv/Kconfig: make direct map manipulation options depend on MMU
Date: Tue, 18 May 2021 10:20:29 +0300 [thread overview]
Message-ID: <20210518072034.31572-3-rppt@kernel.org> (raw)
In-Reply-To: <20210518072034.31572-1-rppt@kernel.org>
From: Mike Rapoport <rppt@linux•ibm.com>
ARCH_HAS_SET_DIRECT_MAP and ARCH_HAS_SET_MEMORY configuration options have
no meaning when CONFIG_MMU is disabled and there is no point to enable
them for the nommu case.
Add an explicit dependency on MMU for these options.
Signed-off-by: Mike Rapoport <rppt@linux•ibm.com>
Reported-by: kernel test robot <lkp@intel•com>
Reviewed-by: David Hildenbrand <david@redhat•com>
Acked-by: James Bottomley <James.Bottomley@HansenPartnership•com>
---
arch/riscv/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index a8ad8eb76120..c426e7d20907 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -26,8 +26,8 @@ config RISCV
select ARCH_HAS_KCOV
select ARCH_HAS_MMIOWB
select ARCH_HAS_PTE_SPECIAL
- select ARCH_HAS_SET_DIRECT_MAP
- select ARCH_HAS_SET_MEMORY
+ select ARCH_HAS_SET_DIRECT_MAP if MMU
+ select ARCH_HAS_SET_MEMORY if MMU
select ARCH_HAS_STRICT_KERNEL_RWX if MMU && !XIP_KERNEL
select ARCH_HAS_STRICT_MODULE_RWX if MMU && !XIP_KERNEL
select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST
--
2.28.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-18 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 7:20 [PATCH v20 0/7] mm: introduce memfd_secret system call to create "secret" memory areas Mike Rapoport
2021-05-18 7:20 ` [PATCH v20 1/7] mmap: make mlock_future_check() global Mike Rapoport
2021-05-18 7:20 ` Mike Rapoport [this message]
2021-05-18 7:20 ` [PATCH v20 3/7] set_memory: allow querying whether set_direct_map_*() is actually enabled Mike Rapoport
2021-05-18 7:20 ` [PATCH v20 4/7] mm: introduce memfd_secret system call to create "secret" memory areas Mike Rapoport
2021-05-19 0:44 ` Andrew Morton
2021-05-19 3:50 ` Mike Rapoport
2021-05-18 7:20 ` [PATCH v20 5/7] PM: hibernate: disable when there are active secretmem users Mike Rapoport
2021-05-18 7:20 ` [PATCH v20 6/7] arch, mm: wire up memfd_secret system call where relevant Mike Rapoport
2021-05-18 7:20 ` [PATCH v20 7/7] secretmem: test: add basic selftest for memfd_secret(2) Mike Rapoport
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=20210518072034.31572-3-rppt@kernel.org \
--to=rppt@kernel$(echo .)org \
--cc=James.Bottomley@HansenPartnership$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=bp@alien8$(echo .)de \
--cc=catalin.marinas@arm$(echo .)com \
--cc=cl@linux$(echo .)com \
--cc=dan.j.williams@intel$(echo .)com \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=david@redhat$(echo .)com \
--cc=elena.reshetova@intel$(echo .)com \
--cc=guro@fb$(echo .)com \
--cc=hagen@jauu$(echo .)net \
--cc=hpa@zytor$(echo .)com \
--cc=jejb@linux$(echo .)ibm.com \
--cc=keescook@chromium$(echo .)org \
--cc=kirill@shutemov$(echo .)name \
--cc=linux-api@vger$(echo .)kernel.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-nvdimm@lists$(echo .)01.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=lkp@intel$(echo .)com \
--cc=luto@kernel$(echo .)org \
--cc=mark.rutland@arm$(echo .)com \
--cc=mhocko@suse$(echo .)com \
--cc=mingo@redhat$(echo .)com \
--cc=mjg59@srcf$(echo .)ucam.org \
--cc=mtk.manpages@gmail$(echo .)com \
--cc=palmer@dabbelt$(echo .)com \
--cc=palmerdabbelt@google$(echo .)com \
--cc=paul.walmsley@sifive$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=rick.p.edgecombe@intel$(echo .)com \
--cc=rjw@rjwysocki$(echo .)net \
--cc=rppt@linux$(echo .)ibm.com \
--cc=shakeelb@google$(echo .)com \
--cc=shuah@kernel$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=tycho@tycho$(echo .)ws \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=will@kernel$(echo .)org \
--cc=willy@infradead$(echo .)org \
--cc=x86@kernel$(echo .)org \
--cc=yury.norov@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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