[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cef36a7e-f652-3c65-2627-5147291b83ea@linux.alibaba.com>
Date: Fri, 22 Jul 2022 20:49:27 +0800
From: tianxianting <xianting.tian@...ux.alibaba.com>
To: Andreas Schwab <schwab@...ux-m68k.org>
Cc: paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, anup@...infault.org, heiko@...ech.de,
guoren@...nel.org, mick@....forth.gr,
alexandre.ghiti@...onical.com, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, crash-utility@...hat.com,
huanyi.xj@...baba-inc.com, heinrich.schuchardt@...onical.com,
k-hagio-ab@....com, hschauhan@...ltrace.org
Subject: Re: [PATCH 4/5] riscv: Add modules to virtual kernel memory layout
dump
在 2022/7/22 下午6:10, Andreas Schwab 写道:
> On Jul 17 2022, Xianting Tian wrote:
>
>> diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
>> index d466ec670e1f..2c4a64e97aec 100644
>> --- a/arch/riscv/mm/init.c
>> +++ b/arch/riscv/mm/init.c
>> @@ -135,6 +135,10 @@ static void __init print_vm_layout(void)
>> (unsigned long)VMEMMAP_END);
>> print_ml("vmalloc", (unsigned long)VMALLOC_START,
>> (unsigned long)VMALLOC_END);
>> +#ifdef CONFIG_64BIT
>> + print_ml("modules", (unsigned long)MODULES_VADDR,
>> + (unsigned long)MODULES_END);
> #ifdef MODULES_VADDR ?
Maybe CONFIG_64BIT is better, it shows more infos(64bit defined, 32bit
not). If use MODULES_VADD, people may doubt which conditions
MODULES_VADD is not defined?
>
Powered by blists - more mailing lists