[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210816144728.1425121-1-heinrich.schuchardt@canonical.com>
Date: Mon, 16 Aug 2021 16:47:28 +0200
From: Heinrich Schuchardt <heinrich.schuchardt@...onical.com>
To: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
Heinrich Schuchardt <heinrich.schuchardt@...onical.com>
Subject: [PATCH 1/1] riscv: select CONFIG_ARCH_KEEP_MEMBLOCK
For analyzing memory blocks we can either use the memblock=debug command
line argument which creates massive output or a debug file system.
Select CONFIG_ARCH_KEEP_MEMBLOCK to provide a debugfs at
/sys/kernel/debug/memblock to analyze memory blocks. The
same is already done for arm, arm64, mips, powerpc.
The actual provisioning of the file system depends on CONFIG_DEBUG_FS.
Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@...onical.com>
---
arch/riscv/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index 4f7b70ae7c31..a6e57614c3fd 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -31,6 +31,7 @@ config RISCV
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
+ select ARCH_KEEP_MEMBLOCK
select ARCH_OPTIONAL_KERNEL_RWX if ARCH_HAS_STRICT_KERNEL_RWX
select ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
select ARCH_SUPPORTS_HUGETLBFS if MMU
--
2.30.2
Powered by blists - more mailing lists