linux-kernel - Re: [PATCH 1/1] riscv: select CONFIG_ARCH_KEEP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ae98dc9e-6892-49c2-24f5-1578b5d4a410@huawei.com>
Date:   Tue, 17 Aug 2021 00:03:23 +0800
From:   Kefeng Wang <wangkefeng.wang@...wei.com>
To:     Heinrich Schuchardt <heinrich.schuchardt@...onical.com>
CC:     <linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
        "Paul Walmsley" <paul.walmsley@...ive.com>,
        Albert Ou <aou@...s.berkeley.edu>,
        Palmer Dabbelt <palmer@...belt.com>
Subject: Re: [PATCH 1/1] riscv: select CONFIG_ARCH_KEEP_MEMBLOCK


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"