From: Steven Price <steven.price@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, linux-mm@kvack.org
Cc: christophe.leroy@csgroup.eu,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] mm: Make GENERIC_PTDUMP dependent on MMU
Date: Thu, 13 Feb 2025 11:23:08 +0000 [thread overview]
Message-ID: <5504fadd-6174-41c4-90a8-d3ae7f76d7f6@arm.com> (raw)
In-Reply-To: <20250213040934.3245750-4-anshuman.khandual@arm.com>
On 13/02/2025 04:09, Anshuman Khandual wrote:
> There is no page table dump without a MMU. Make this dependency at generic
> level and drop the same from riscv platform instead.
>
> Cc: Paul Walmsley <paul.walmsley@sifive.com>
> Cc: Palmer Dabbelt <palmer@dabbelt.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: linux-riscv@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-mm@kvack.org
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
As Christophe has pointed out - this is broken. The select will override
the dependency you've added in GENERIC_PTDUMP. Generally have "depends
on" for symbols that are "select"ed is broken. I'd suggest just dropping
this patch.
Steve
> ---
> arch/riscv/Kconfig | 2 +-
> mm/Kconfig.debug | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index 7612c52e9b1e..c4cdba6460b8 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -112,7 +112,7 @@ config RISCV
> select GENERIC_IRQ_SHOW_LEVEL
> select GENERIC_LIB_DEVMEM_IS_ALLOWED
> select GENERIC_PCI_IOMAP
> - select GENERIC_PTDUMP if MMU
> + select GENERIC_PTDUMP
> select GENERIC_SCHED_CLOCK
> select GENERIC_SMP_IDLE_THREAD
> select GENERIC_TIME_VSYSCALL if MMU && 64BIT
> diff --git a/mm/Kconfig.debug b/mm/Kconfig.debug
> index a51a1149909a..c08406760d29 100644
> --- a/mm/Kconfig.debug
> +++ b/mm/Kconfig.debug
> @@ -214,6 +214,7 @@ config DEBUG_WX
> If in doubt, say "Y".
>
> config GENERIC_PTDUMP
> + depends on MMU
> bool
>
> config PTDUMP_CORE
next prev parent reply other threads:[~2025-02-13 11:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 4:09 [PATCH 0/4] mm: Rework generic PTDUMP configs Anshuman Khandual
2025-02-13 4:09 ` [PATCH 1/4] configs: Drop GENERIC_PTDUMP from debug.config Anshuman Khandual
2025-02-13 11:23 ` Steven Price
2025-02-13 4:09 ` [PATCH 2/4] mm: Make DEBUG_WX depdendent on GENERIC_PTDUMP Anshuman Khandual
2025-02-13 11:23 ` Steven Price
2025-02-13 4:09 ` [PATCH 3/4] mm: Make GENERIC_PTDUMP dependent on MMU Anshuman Khandual
2025-02-13 7:30 ` Christophe Leroy
2025-02-13 11:23 ` Steven Price [this message]
2025-02-14 6:49 ` Anshuman Khandual
2025-02-13 4:09 ` [PATCH 4/4] mm: Rename GENERIC_PTDUMP and PTDUMP_CORE Anshuman Khandual
2025-02-13 7:38 ` Christophe Leroy
2025-02-14 7:17 ` Anshuman Khandual
2025-02-24 11:12 ` Christophe Leroy
2025-02-13 11:23 ` Steven Price
2025-02-13 11:49 ` Christophe Leroy
2025-02-14 7:26 ` Anshuman Khandual
2025-02-24 11:13 ` Christophe Leroy
2025-02-14 7:19 ` Anshuman Khandual
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=5504fadd-6174-41c4-90a8-d3ae7f76d7f6@arm.com \
--to=steven.price@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
/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