[PATCH 1/1] riscv: select CONFIG_ARCH_KEEP_MEMBLOCK
Kefeng Wang
wangkefeng.wang at huawei.com
Mon Aug 16 09:03:23 PDT 2021
On 2021/8/16 23:52, Heinrich Schuchardt wrote:
> On 8/16/21 5:30 PM, Kefeng Wang wrote:
>>
>> On 2021/8/16 22:47, Heinrich Schuchardt wrote:
>>> 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.
>>
>> Hi,for riscv, it don't use memblock(eg, no provide pfn_valid to use
>> memblock),
>>
>> we could call memblock_discard() to discard memblock private memory
>> to save
>>
>> some memory, right? So I think we don't need this config for now.
>
> What do you mean by "it don't use memblock?
Sorry, it should be "the riscv don't use memblock after the page
allocator is initialized"
More information about the linux-riscv
mailing list